Reputation: 275
I am testing for the first time the Azure Service Bus integration with Logic Apps. To run an easy sample, I've created a queue in a Service Bus, and two logic apps: the first one writes a message in the queue every minute, the second one reads a message every minute. The first app works fine, and I can see that my one and only queue gets populated with messages. The second app, instead, always return status "skipped" on the trigger, as if the queue was empty, even though I can clearly see from the Azure Portal that the queue is not empty.
The messages also seem to be removed by the active queue and moved to the Dead Letter queue with reason MaxDeliveryCountExceeded.
Since there are not many options to play around with in the Azure logic app designer, and this is a very basic example, I am at a loss to where I might be wrong. I am sure it is something simple, but I just can't make it work.
Here is what gets returned by the app that tries to read the queue:
Upvotes: 0
Views: 1828
Reputation: 275
Apparently, as a mistake, I put the lock timeout as only 1 sec when I created my queue. This was not enough to process the messages by my app (which was sending a test email via Outlook.com connector). The messages then was put in the dead letter queue and the app showed the trigger as "skipped".
Upvotes: 2