Check a workflow result in its destination
Connect a run’s status and output with the record or message it was intended to produce.
Check a workflow result in its destination
A completed run tells you what the workflow reports. To confirm a business result, check the destination too.
Read the run in context
1. Open the exact workflow and choose Run History. Find the run you mean by its mode, revision and displayed time.
2. Read its status and available output. Match the result to the saved definition and input, rather than combining details from different runs.
3. Identify the intended effect. A literal comparison with no action nodes should not create a task or send a message. Its useful result is the comparison output.
Check a real effect separately
4. For a record change, open the actual target in its module and compare the important fields. Match the workroom, record identity and intended value.
For a message, check the intended destination and content. A sent record is not necessarily proof that the recipient read it.
5. Compare the result with the state before the run when you need to know whether this run caused the change. A record that already had the desired value is not proof of a new effect.
Resolve disagreements before another run
If the run says completed but the destination still has the old state, check identity and timing before drawing a conclusion. If you cannot determine whether an effect happened, investigate it before rerunning.
Your result is a specific answer: which revision and mode ran, what it returned and what the destination now shows. Avoid the broader claim “the automation works” when you checked only one field or one delivery stage.
A unique title helps you search, but it does not automatically prevent duplicate effects. Do not run again solely to replace an unclear confirmation with a cleaner-looking history entry.
Continue learning
In this series: Design and check workflows — guide 6 of 8.
Turn what you learned into the way the team works.
Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.