Failed action has 'run after failure' but flow still fails and gets turned off

(1) Share

Report

Posted on by BB-12081421-0

Hi,

I have a flow that checks if a future, current or passed employee has an O365 account. Normally accounts are blocked when an employee leaves the company and deleted after 90 days. We want a sharepoint list that doublechecks.

Once a day the flow is triggered
We 'get items' from a sharepoint list of all employees
We use ‘get user profile (v2)’ in a loop to get every employees O365 profile
If they have a profile -> the user has an account, we check if it’s enabled or disabled and write this to our sharepoint list
If they don’t have a profile -> ‘get user profile (V2) fails. We’ve set a ‘run after fail’ and write ‘no account’ to our sharepoint list.

No issues there. It works perfectly.

Except, when ‘get user profile(V2)’ fails power automate considers the entire flow a failure, even though a run after fail is set. After a while it turns the flow off automatically because it keeps failing.

I can’t use a terminate action, because my loop still needs to cycle through all the other employees.

Any ideas?

Thanks

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Pstork1 69,417 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

It sounds like you are using the Run After inside the loop. That will work, but it doesn't prevent the error from rolling up to the containing loop. So make sure you have at least one action after the loop finishes set to run when the loop succeeds or fails. Here's a screenshot of an example. You can see that the Get user profile failed and the run after action runs. But the flow itself failed until I added the final Compose set to run if the loop succeeded or failed.

Was this reply helpful? Yes No
abc 123 789 Moderator on at

Like (0)

Report
Copy link

Link copied!

Due to the fact that Microsoft takes it upon themselves to turn off a Flow that "Fails", I now try to terminate with a "Cancel", instead of "Fail", whenever possible. For example, logical errors get a Cancel, but calls to a Child Flow that choke still get a Fail.

To do this, initialize a variable, called strFlowStatus, to "Success".

Whenever a trapped error happens, set the variable to "Cancel" when in that branch.

If the Flow truly fails, meaning a non-bizlogic fail, then set the variable to "Fail".

At the end of the Flow, add a Switch Action, and Handle each status, "Success", "Cancel", and "Fail", separately.

For extra credit, when there is a true Fail, I send an email to myself.

Was this reply helpful? Yes No