Queue assigns wrong Sequence number when resubmitted from a partitioned queue

[DeepakMohanSingh]

Description

Actual Behavior

I face an issue when resubmitting a message from a partitioned queue to a conventional queue using dot net latest SDK. As partitioned queue assigns a sequence number that is relative to the partition (the topmost 16 bits reflect the partition identifier), when I resubmit a message from this partitioned queue to a normal queue (which has just 3-4 messages with sequence number like 1,2,3,4), the new message that lands on the queue has a strange sequence number! (The sequence number assignment looks like how it looks in the partitioned queue - 16 digits for example).

Expected Behavior

Shouldn't this sequence number be something like "5" in my conventional queue (I mean, relative to the existing messages in my queue)?

Repro steps:

ServiceBusReceivedMessage _message = await receiverClient.PeekMessageAsync(); // receiverClient connects with partitioned queue
ServiceBusMessage message = new ServiceBusMessage(_message);
await senderClient.SendMessageAsync(message); // senderClient connects with conventional queue

Other problems due to this behaviour:

• I am not able to purge the messages with such sequence number. I tried with my code, and with Service Bus Explorer too.

[SeanFeldman]

Do you see this with a single namespace or can reproduce with other namespaces?

[EldertGrootenboer]

We have added this to our backlog to investigate the behavior you are seeing. Will come back to this issue when we have more information.

[EldertGrootenboer]

Thank you for your feedback on this item. We are currently doing active investigation on this feature, and expect to have more to share around it in the next couple of months.

[EldertGrootenboer]

We have identified a client side issue for this, hence closing this issue. The progress for the fix can be tracked at https://github.com/Azure/azure-sdk-for-net/issues/39886.