Azure Service Bus Topic Subscriber receiving messages not in order

0
votes

I am using azure service bus topic and I have enable session for it's subscription.

With in the my logic app i am inserting data using sql transaction which are coming from topic I am using topic Subscription(peek-lock) and in subscriber level concurrency is set to default as follows

enter image description here

According to my Understanding, my logic app(subscriber) should read ALL the messages and have to processed in FIFO
my logic app is like

enter image description here

which means it should insert data to the table in ordered manner

however when i checked in the trigger log it shows correct order but in database level you can see the order is not happening

enter image description here

1
azureazureservicebusazure-servicebus-topics
The LImit is turned off, meaning multiple Logic App instances will run. You will need to enable the limit to have a single instance processing messages. – Sean Feldman
true we can set limit in to 1 and this problem will solve and another will create since i am inserting data in to database and if whole process takes 1 min to complete, maximum records that i can insert per day will be 1440. any other suggestions? – Thili

1 Answers

2
votes

Message ordering is a delicate business. You can have either message ordering or concurrent processing, but not both. The moment you make message ordering a must, you lose the ability to have concurrent processing. This is correct for both, Azure Service Bus Sessions and Logic Apps concurrency control. You could process multiple sessions, but each session would be still restricted to a single processor. Here's a post about it.