Actions in this flow may result in an infinite trigger loop. Please ensure you add appropriate conditional checks to prevent this flow from triggering itself.
I have searched through various forums, but for the above error, I only found examples where the table is in SharePoint. However, my table is in Dataverse.
I have a table called Joints, and I want it to update a field value when the trigger "When a row is added, modified, or deleted" is activated. Everything is successful, but I keep entering an infinite loop, and eventually, the flow fails. I understand that I need to define Trigger Conditions for the "When a row is added, modified, or deleted" trigger.
my response to the Trigger Conditions is: `@not(equals(triggerBody()?['_modifiedby_value'],'6ff19ec8-d7e0-ed11-a7c6-00224804bdee'))`.
However, this isn't working correctly, and the cycle repeats again. What is your solution?
The reason seems to be simple, actually the trigger when row is created/modified/deleted starts the flow when the record in dataverse is created/modified/deleted. So when you use the update row action in dataverse- this will eventually result in trigger running again the flow.
This trigger condition means the flow should run only if the modified by person is other than who is having id - 6ff19ec8-d7e0-ed11-a7c6-00224804bdee - I assume this is yours- but this may not helps, for example - your flow is ran using a service account, now when it updates the dataverse row- the flow can be trigger again if it trigger condition turns out to be true.
May be you should make it more better by writing the trigger condition based on a column name- let's say- when the column Status is equal to New- run the flow- else not- this will be better if column value would change.
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
6
Share
Report
All responses (
Answers (
