Answered

Error Handling for HTTP Request in a for each loop

(0) Share

Report

Posted on by DH-25031424-0

I have an for each loop with a Http Request action. If the user in a sharepoint list doesnt exist in entra than the Request runs on error.

Now my flow runs on error though I have following error handling

why is this and how can I change this, that my whole flow doesnt run on error.

I am happy about any help!

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (1)

VictorIvanidze 13,079 on at

Like (0)

Report
Copy link

Link copied!

Try to use the classic editor.

Was this reply helpful? Yes No
Verified answer

DJ_Jamba 2,837 Moderator on at

Like (0)

Report
Copy link

Link copied!

In addition to the comment by @VictorIvanidze
After your two parallel actions (Left side success, right side fail) add a Compose action and put anything in it e.g. OK
In the run after setting of the Compose there will be be 2 actions listed:
The compose needs to run when the JSON action is skipped or is successful OR when the Scope action is skipped or is successful

Configure the Compose Run After as shown in the screenshot:

Was this reply helpful? Yes No
DH-25031424-0 4 on at

Like (0)

Report
Copy link

Link copied!

@DJ_Jamba your suggestion with the compose action was my solution. It was independent of the editor. i also had my phenomenon in the old designer.

To learn something else here. Why a Compose action. Was that simply to fill a gap?
Is this normal in a For Each loop? I would have thought that if the last entry in a loop runs on Success, then so does the loop itself.

In any case, many thanks for the quick answers! @VictorIvanidze & @DJ_Jamba

Was this reply helpful? Yes No
DJ_Jamba 2,837 Moderator on at

Like (1)

Report
Copy link

Link copied!

@DH-25031424-0

Your thinking is correct. The compose action is the simplest action to throw in (you could set a variable too but for me that was overkill).
We don't really care about the action, but rather the way we can configure the Run After property.

I too shared your frustration when I handled an error but the flow still reported as failed (when it actually didn't) so through trial and error I discovered that an additional action was required.

I have absolutely no idea why the flow behaves this way 😅 - it's another nuance I add to my ever-growing Power Platform nuances list

d(-_-)b

Was this reply helpful? Yes No