How do you troubleshoot a failing flow?

Nødvendige verktøy

• Access to the flow — You must be an owner or co-owner to view the run history.

Find the cause

1. 1.Open the run history and find the first failed run

   Not the last one—the first. Whatever went wrong started there, and everything after that is usually a knock-on error. The timestamp often tells you what changed.

2. 2.See which step failed and what went into it

   The run history shows the input and output for each step. There you can see whether the field was empty, the text was too long, or the response differed from what was expected. This is almost always enough to understand the cause.

3. 3.Check the connection

   Error messages about missing permissions or sign-in indicate an expired connection or that the owner has left. This is the most common single cause.

Correct and prevent

1. 4.Fix the cause, not the symptom

   If the field was empty, add a check for that instead of removing the step. Otherwise, the error will reappear in another form.

2. 5.Rerun the failed runs

   Failed runs can be resubmitted after the issue has been fixed. Consider whether this is appropriate—some flows should not be run twice, such as those that send emails to customers.

3. 6.Set up an alert if one is missing

   The real failure is that the flow failed without anyone noticing. Set up an alert to a shared mailbox before proceeding.