Answered

Possible Bug in the Flow Status

(0) Share

Report

Posted on by AS-24061420-0

I have a cloud flow that has been reported as failed a couple of times today. After reviewing the run history, it appears that the flow actually completed successfully and produced the expected outcome.

The relevant part of the flow is configured as follows:

Run Block 1
Run Block 2 only if Block 1 fails
Run Block 3 only if Block 2 fails

In the affected runs, the execution path was:

Block 1 ran and failed
Block 2 ran and failed
Block 3 ran and succeeded

Since Block 3 is the final fallback and completed successfully, the overall process behaved as intended. However, the run was still marked as Failed.

In similar scenarios where only one block fails and the subsequent fallback succeeds, the overall flow status is reported as Succeeded. The difference here seems to be that two consecutive actions failed before the successful fallback was reached.

Could you please review the attached screenshot and confirm whether this behaviour is expected? My assumption is that this may be a bug, but I would like to verify that before raising it formally.

Screenshot 2026-0...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (2)

Sort by

Verified answer

David_MA 14,956 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Based on your image, it looks like there are no more actions in your flow after the apply to each action. If you don't want the flow to be tagged as failed, you need to add something after the apply to each that runs on success and fail or have a parallel branch like you do for the Create file when that fails with one for success and one for fail. I hope this makes sense. You basically need a catch for the apply to each that fails.

Was this reply helpful? Yes No
Verified answer

chiaraalina 2,425 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @AS-24061420-0

This is not a bug.

Configure Run After only determines whether the next action is allowed to execute. It does not remove the failed status of previous actions.

Because the run still contains failed actions, Power Automate reports the overall flow as Failed, even though the fallback logic produced the desired outcome.

If you need the flow to finish with an overall Succeeded status after handling these failures, add a Terminate action with status Succeeded.

This ends with an overall Succeeded.

Hope it helps!

Was this reply helpful? Yes No