I have a flow in which the success or failure of one step in an Apply to Each loop should not prevent the following step from running, however, all subsequent steps seem to get skipped regardless. Does anyone have any ideas?
The logic looks like this
Apply to Each (excel table) row
Add to Group [rowUser UPN]
On success: set rowOutcome = "Group load successful"
On fail: set rowOutcome = "Group load failed"
Update Excel (current) row
I get the correct run-after action for the Add to Group action (success or fail), but nothing after that runs. What gives?
I would expect the compose + update steps to run regardless of the prior run-after branches but the compose step fails and I do not get the rowOutcome updated.
Compose step Run-After is configured as follows
The result in Run History is
Originally I had no Run After configured for this step, since the outcome of the previous steps does not matter, I want the compose and succeeding update to run regardless, but it skipped in that test too.
Check out new user group experience and if you are a leader please create your group
On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks
Check out how to claim yours today!
Test your skills now with the Cloud Skill Challenge.