Run Detail And Step Logs
Inspect one workflow run, its steps, context, outputs, and errors.
Run detail shows exactly what happened during one workflow execution.
Open A Run
- Open Workflows.
- Open the workflow.
- Go to Runs.
- Select a run.
The run detail shows status, trigger type, started time, finished time, duration, triggered-by user, step counts, context, and step logs.
Use run detail when a workflow produced the wrong result, skipped a path, failed partway through, or needs proof of what happened.
Open run detail before editing the workflow. The run usually shows whether the problem is trigger data, a condition, permissions, provider connection, or an action configuration.
Read Step Statuses
Steps can be pending, running, succeeded, failed, or skipped. Failed steps show where to start troubleshooting.
Read the run from top to bottom. The first failed or unexpected skipped step is usually more useful than the final status because later steps may only reflect the earlier problem.
Do not stop at the final status when customer-facing work is involved. A run can finish while still creating an unexpected message, task, or record.
Compare Expected And Actual Output
Before rerunning a workflow, write down what the run should have done. Then compare that expectation with step inputs, outputs, skipped paths, created records, sent messages, and errors.
Conditions, Delays, And For Each
Run detail can explain whether a condition matched, when a delay is waiting until, or how many items a For Each step processed.
For conditions, compare the input value with the operator and expected value. For delays, check the resume time and timezone. For For Each steps, check the collection size before assuming every record was processed.
Context And Outputs
Review the context panel to see the record, user, trigger, and values available to the workflow. Review step outputs to see what each action returned to later steps.
If a later action has an empty field, trace back to the step that was supposed to provide that value. The issue is often a missing variable, skipped condition, or action that returned no record.
If the wrong customer or record was used, inspect the trigger payload first. Fixing an action will not help if the workflow started with the wrong source record.
Cancel A Run
Queued or running runs can show a cancel action. Cancel only when the run should not continue.
Canceling stops future work for that run; it does not automatically undo actions already completed. Review completed steps before rerunning or manually cleaning up records.
If a run already sent a message, created an invoice, or updated a customer record, decide how to clean that up before retrying.
What To Collect For Debugging
When reporting a workflow issue, collect the workflow name, run ID or URL, trigger type, run status, failed step name, error text, and the record that started the run.
Also note whether the workflow was recently edited, published, paused, or reconnected to an app. Recent changes often explain a failed run.
If customer-facing work was affected, also collect the related customer, invoice, document, ticket, task, or appointment so the cleanup path is clear.
Cleanup After A Bad Run
After a bad run, list completed actions before rerunning. Messages, invoices, tasks, records, and provider calls may need manual cleanup or customer follow-up before another run is safe.