I have a azure service bus queue which has a number of message's within it. And have a logic-app using a manual trigger. I then add a "Get messages from a queue (peek-lock)" action to the app to get the messages from this service bus and set the maximum message count to "170". But when it's triggered it only picks 1 message. Can someone explain why this is. And why it's not picking up 170 messages.
Thanks
@IqbalZafar-4376, Thanks for reaching out. Can you please confirm whether you are using the session property for the action Get messages from a queue (peek-lock)?
The only scenario that i can think about will be when you are using the session while retrieving the messages where messages will be returned from a single partition in case of partition entity with session enabled. The other scenario could be when a single message content might be equal to the maximum message size of that SKU.
Hi @IqbalZafar-4376 ,
Just reaching ouch to see if you have managed to identify the problem.
Is there anything else we can do to help?
hi @IqbalZafar-4376 ,
this is how I've done it:
-added the "get message from a queue (peek lock)"
-added an action to process/receive the messages. on this case, just a compose to troubleshoot
-inside the compose I've added the "Current item" from the "ForEach"
After succeeding , I switched to pull from a queue with Partitions. That produced the problem. When queue has partitions it will pull 1 message only.
I can't find an option to handle queues with partitions in the "get message from a queue (peek lock)" task
Is you queue partitioning enabled?
Are you looping through your messages?
18 people are following this question.
