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?