Does this happen often?
I don't have a solution, but it seems like it would be better to come up with a different process.
Like I'm thinking about people who set up flows that trigger on an email inbox when mail is received. It might take a few minutes for the flow to trigger after the email arrives. However, they need the flow to trigger immediately or it will be a problem with the overall process.
The only solution is to change the process of how they plan to do work. The plan should not require immediate email notice to function properly since that is not a capability they have.
You want this flow to trigger on some kind of specific file change using the broad trigger of whenever a file is changed. However, you're going to continue changing the file. You do have some kind of method for blocking future flows, but it doesn't happen fast enough.
You are limited by the speed of when a flow can trigger. That is not going to change.
The process you want to implement needs to change due to system limitations.
Like instead of using the active file to trigger the flow, could you use like a drop folder or something that uses a second copy file? So maybe when you drop a file in the folder it triggers an approval flow. Either the flow runs off that document or whatever. Or you could maybe hyperlink the approval back to the active document?
I really don't know how to change it, but I think a change to the process would be better.
Bc I can't think of a way to prevent Action2 from happening when it is conditional on a result from Action1; when Action1 has not even been initiated.
Who knows, maybe some power automate wizard will come step on me with some fancy tricks and solution.
