Hello,
I have 3 flows that must be started in a specific order.
Flow 1 is run automatically once a new Microsoft Forms response has been made.
At the end of this flow, I have an 'Update item' action that fills a plain text field named "WF2" with the value of 'No'.
Flow 2 has a trigger condition set to the following.
@not(equals(triggerBody()?['WF2'],'No'))
So if the value of 'No' had been entered at the end of Flow 1 then Flow 2 will start.
At the end of the flow I have an 'Update item' action that fills a plain text field named "WF3" with the value of 'No'.
Flow 3 has two trigger conditions set to the following:
@not(equals(triggerBody()?['StartWF'],'No'))
The first Trigger Condition is used to re-trigger the workflow is an Approval item later in the Flow hasnt been approved after 29 days (this is to get around the 30 timeout limit).
@not(equals(triggerBody()?['WF3'],'No'))
The second Trigger Condition is used to check whether the field "WF3" (applied at the end of Flow 2) has been filled with the value of 'No'.
The Problem I seem to be facing here is that Flow 3 appears to be triggering before or at the same time as Flow 2 and because specific things are not being applied in Flow 2 first, this is causing Flow 3 to not run correctly. Flow 3 shouldn't be running until Flow 2 has completed.
Any thoughts on how I can get around this?
I wouldn't be surprised if there's an issue in my Trigger Condition expression for WF3