You’re offline. This is a read only version of the page.
I have set up my flow to check if a row in an excel file exists, and if it does not, create a new row. The second task should only run when the first one fails (since it is configured to run after only if failed). Yet my flow failed today (normally runs fine) due to no row being found. Any ideas why this might have failed and not run the next task?
Hi @brendan_o ,
Is it possible that your workflow contains multiple connectors with the 'run after' configuration?
If that's the case, when a connector fails, this 'failed' status is propagated throughout the workflow. When it reaches a connector that has the 'run after: has failed' option enabled, that particular connector becomes active. It performs its intended actions and then transitions to a 'status: successful' state. However, when this 'status: successful' status reaches the second connector with the 'run after: has failed' setting enabled, the second connector won't be activated.
I hope this explanation helps to eliminate any confusion.
Share
Report
All responses (
Answers (
17
