Limitations when working with Azure Service Bus

Although QueueExplorer makes queues and messages look similar to folders and files, under the hood they are still first-in first-out queues. For some operations QueueExplorer will perform Receive and/or Send operations. Send operation will create new message and they’ll be put at the end of the queue.

General limitations

• In order to delete, schedule, defer, etc. message from a middle of a queue, QueueExplorer has to receive messages which come before wanted one, and to “Abandon” them afterwards. That increases Delivery Count of these messages, and if it reaches 10 (default, can be changed from queue properties), these messages will be deadlettered.
• When you load, copy, drag&drop or edit message it will go to the end of queue.
• Since these messages are actually new messages in Azure Service Bus, some properties will be changed like time sent, time arrived, DeadLetterSource, etc.
• QueueExplorer doesn’t update display in real time. If some other application or another QueueExplorer window modifies some queue, you have to use “Refresh” to see these changes.
• Some operations could fail or produce undesirable results if messages are removed in the mean time by some other program. It’s advisable to stop other processes that use queue while operations like copy, move, etc. are performed.