Workflow Runs

Every workflow execution is recorded independently of the entry status. Open an entry and choose Workflow Runs to inspect what started, which path ran, and where a failure occurred.

Run list

Each row shows:

• Workflow name or ID
• Trigger label and trigger type
• Status: started, completed, or failed
• Start time and duration
• Executed step count
• Top-level error, if any

Runs are paginated 15 at a time.

Run details

Open a run to inspect its trigger and individual step executions. Diagnostics can include the step type and label, entered/ended timestamps, status, inputs, outputs, chosen connection/path, and recorded error.

Earlier step outputs are the same values downstream references such as workflow:current.steps.… resolve during that run.

Diagnose a failure

1. Confirm the trigger is the one you expected.
2. Find the first failed step, not merely the final workflow error.
3. Check resolved inputs and which environment/template/reference was selected.
4. Inspect the error path and downstream steps that did or did not run.
5. Correct the draft workflow or external configuration and publish where required.

FormWork does not change a complete entry to an “error” entry when a workflow fails. Always use the run record as the source of automation status.

Common patterns

• A condition choosing the wrong route usually indicates a reference, operator, or resolved-value mismatch.
• An extension action can fail because its environment is disabled, credentials are wrong, input mapping is incomplete, or the remote service rejected the request.
• An email/PDF failure may come from missing template data or invalid rendered content.
• A downstream step not appearing means its connection was not selected or an earlier step stopped the run.

For configuration, see Workflow Basics, Step Types, and References & Data.