Flow Designer failures
Quick answer
Read flow execution details, find the failing step, and fix the causes that repeat.
Key takeaways
- Execution details show inputs and outputs per step
- No execution usually means the trigger never matched
- Continue on error hides failures, choose it deliberately
- Alert when a critical flow stops completing
Start with the execution
Open the flow, choose Executions, and pick the run. Each step shows inputs, outputs and duration. Ninety percent of flow tickets are answered here without opening a script.
Frequent causes
The same handful of issues recur.
- Trigger condition never matched, so no execution exists at all
- A record was updated by a rule after the trigger, changing the data the flow read
- Wait for condition never satisfied because the condition uses a field the process never sets
- An action failed on an external call and error handling was set to continue, hiding it
Preventing repeats
Set error handling explicitly on every external action, log a correlation value at the start, and add a flow that alerts when a critical flow has not completed within its expected time. Silent automation failures cost more than loud ones.
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
Where do you see the inputs a step received?
- A. System log
- B. Flow execution details
- C. Transaction log
- D. Event log
Show answer
B. Flow execution details
Execution details record inputs, outputs and timing per step.
No execution record at all usually means
- A. The flow is broken
- B. The trigger condition did not match
- C. The instance was down
- D. ACLs blocked it
Show answer
B. The trigger condition did not match
No trigger match means the flow never started.