Service Bus Communication Error

Question

Good day,

I have a logic app that reads from a session-enabled queue. At most, there may be 2 instances of this running in parallel.
However, each instance would never use the same session ID when reading from queue as they represent different categories of data upon which the session ID is based.

On an ad-hoc basis (happens now and then), the following error is being experienced when trying to complete the message after having read it:

Communication with the Service Bus namespace '<service-bus-name>.servicebus.windows.net' and '<service-bus-queue>' entity failed.

I then attempted to introduce a retry loop, but the subsequent attempt then yielded the following error:

This messaging entity has already been closed, aborted, or disposed.

Any further attempts presents the following error (due to eventual token timeout I suppose):

No session available to complete the message with the lock token '<token>'.

Could you please explain why the communication error occurs, and how this may be resolved?

Answer 1

@Razeen Hendricks Apology for the delay. Communication expection is the Transient error and logic app does handle these type of errors.
As you are using the session enabled queue so all the messages are send to the same partition for the same sessions. In case if there is any service updates/issue for that partition then there would be some expection/error during that time. As logic app service bus connector does have retry in place but if it failes till the max retry then the exception is throw and your workflow failed. But the next runs (once the upgrade completes) should eventuately suceeded and it should not effect your workflow but you should few runs getting failed during that time.

If you are observing these error for every run then I will suggest you to open as support ticket with us. If you don't have the support plan then please let me know so we can connect offline and assist you further.