Weird behavior of SQL connector with on-premise data gateway

[hajekj]

Hi, so we are hitting a very weird behavior when using the SQL connector in combination with on-premise data gateway.

When a Flow executes a stored procedure (select item by ID from table) we usually get a single response (since the ID is primary key etc.). However we noticed that in some situations, where the flow is triggered at the nearly same time (with different IDs) the result of the stored procedure is returned with 2 or more results (they all have different ID, only one has the correct one). So my question is, whether this is expected behavior and why is it happening?

So far, we are thinking that it is due to the use of stored procedure, that the result is just "batched" together when the answer is read by Flow by the data gateway. Is there any way to prevent this? We tried checking the logs of on-prem data gateway, but it didn't have any indication to why this might be happening.

[v-yamao-msft]

Hi @hajekj ,

Could you show me more details on how is your stored procedure configured?

And a screenshot of your flow would be helpful for me to reproduce this issue.

I am looking forward to your reply.

Best regards,

Mabel

[MatejSamler]

Hi @v-yamao-msft ,

Here, you can see the flow snipped that uses the procedure. The condition inside the loop was added after the thing @hajekj described happened, as a precussion. 

And here is the stored procedure.