Power Automate: Infinite Trigger Loops 

Ever had a Power Automate Flow trigger itself and run on and on and on? Annoying isn’t it?
Here I will show you a couple of methods you can try to break the loop, how to build trigger condition expressions with the intellisense tools, and how to manage some of your flows with a service account “without paying a monthly subscription.”
In this video
-------------------
01:53 Trigger Conditions
03:45 Create a Flow with a Service Account
07:35 Check how soon the trigger was from the last update
Expression to check Editor
------------------------------------------
@not(equals(triggerOutputs()?[‘body/Editor/Claims’],’i.0#.f|membership|user@domain.com’))
Change user@domain.com to the account you are using to manage the flow flow
Change Claims to Email and remove the i.0#.f|membership| if you want to use the email address.
Expression to Check Date/Time
---------------------------------------------------
@not(lessOrEquals(ticks(triggerBody()?['Modified']),ticks(addMinutes(triggerBody()?['Processed'],1))))
Change Processed to the name of your Date/Time Column
Change the addMinutes to addSeconds if you want a shorter time
Change the number at the end to the time gap you want to check. The bigger the number, the longer it has to be before a user updates it.
IMPORTANT: If you also included a delay following the "File locked for shared use" solution ( • Power Automate: Error ... ), the "1" at the end of the above trigger condition, needs to be larger than the delay time you set. At least 6 minutes is recommended, but I would start at around 10 and work down until it stops working.
NOTE: Take a look at SharePointPro's video for an alternative look at this problem: • Preventing Infinite Lo...