Logic App : Service bus throwing error

Saurabh Moghe 1 Reputation point
2022-11-23T00:05:56.38+00:00

I am using service bus queue with logic app. Sometimes we are getting following error in logic app when we remove the message from queue.
No session available to complete the message with the lock token "" nclientRequestId : ""

And sometimes we are getting following error.

Communication with the Service Bus namespace 'XXXXXX.servicebus.windows.net' and 'sbq-notifications' entity failed.
Channel:uuid:XXXXXXXX-ab79-48d0-9e55-3e4408940770;id=11;Link:65335;Action:http://schemas.microsoft.com/netservices/2011/06/servicebus/SbmpMessageReceiver/UpdateMessageState
TrackingId:XXXXXXXX-ba21-428d-88ff-e671684932e3_G0_B12,
SystemTracker:net.tcp://XXX.XX.XX.XX:21004/1/Runtime, Timestamp:2022-11-08T04:20:11\r\nclientRequestId: XXXXXXXX-d040-4771-a70b-2ac898642be9

I am not sure why this is happening and how to handle it in logic app.
263150-logic-app-service-bus-no-session-issue.png

Azure Service Bus
Azure Service Bus
An Azure service that provides cloud messaging as a service and hybrid integration.
593 questions
Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,991 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. JananiRamesh-MSFT 23,646 Reputation points
    2022-11-24T14:57:30.107+00:00

    Hi @Saurabh Moghe Thanks for reaching out. please make sure if you have selected the "Next available" value in the Session id field in the Trigger. "No session available to complete the message with the lock token" generally means that the lock token that your application is using to complete the session does not exist or become invalid.

    The other possible reason could be the limit as mentioned here. Please confirm if there are more than 1500 unique messages that are sent to your queue when you have observed that the logic app failed with the error : No session available to complete the message with the lock token

    If it is the above case in your scenario then unfortunately as of now this is the hard limit of the connector, you can always pass your feedback and suggestions in our feedback page https://feedback.azure.com/d365community/forum/cb47c115-7926-ec11-b6e6-000d3a4f032c. The suggestion would be to handle this exception in logic app and retry again during the high load when you may have 1,500 unique sessions.

    If you have a support plan, then I will suggest you open a support ticket with us as this would require a deeper investigation in our backend logs to understand what happened and to identify the exact cause. If you don't have support plan, then please let me know so I can assist you further.

    Do let me know if you have any queries.

    0 comments No comments