You’re offline. This is a read only version of the page.
9
I have a Logic App that reads data from an Azure SQL table and creates a GL Journal in D365. This works 90% of the time but every once and a while (a couple times a week) one of the entries in the journal lines will fail with this error:
I think I am going to call this resolved. I was looking back and it has only failed one time in the last month (ever since I set the concurrency to 1). I think when that fail happened I assumed that the concurrency did not help but it looks like it did. I will just chalk that one fail up to a fluke. If it starts happening regularly again I will submit another post. Thank you.
Hi @MarkGilbert ,
Could you please share the screenshot of the flow?
Could you please make sure that you don't have any other flow would run at the same time to lock the table?
If not, I suggest that you could contact Microsoft for any help on this issue.
Best regards,
Alice
Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I am very sure that no one else , no other app or person is trying to access the journal that I am creating.
Hi @MarkGilbert
When flow actions run, they might lock the resource they are writing to as if it was a database that locks table/rows/columns. This can be related to more that one user adding records at exactly the same time so you are getting this error message. Unfortunately, Flow doesn't have a setting nor a way to fix this scenario
Best Regards,
#1
WarrenBelz
146,524
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,906
Most Valuable Professional
Share
Report
All responses (
Answers (
