Logic App Sql Connector as trigger fires many threads

0
votes

I am using a Sql Connector as a trigger in my Logic App

  • Action 1 - Trigger every two minutes with data available query as select count(*) from Foo where status = "new" and poll data query as select id, name, status from foo where status = "new";
  • Action 2 - processes data;
  • Action 3 - uses another sql connector to update the foo table status to "complete";

As you can see from the run image attached, several threads are kicked off for the one entry that is in my db. Is this normal, a defect or just the wrong way to flow the app?

1
azureazure-logic-apps

1 Answers

0
votes

From your question I understood that you put two SQL Connectors one to poll the data and one to update the data which is polled.

If above is the case mean you are going wrong direction you should not use 2 SQL Connectors to complete your work. you should write update statement in your polled query only.

EX: select id, name, status from foo where status = "new";UPDATE foo SET status='complete' WHERE status = 'new' simply append your update query with semicolon as delimiter