Agiled Docs

Workflow runs show each execution of an automation.

Use runs as the audit trail for automation. The builder shows what should happen; runs show what actually happened.

Open Workflow Runs

Open a workflow, then select Runs from the workflow toolbar. You can also open the runs page from the workflow builder after publishing or manually triggering a workflow.

The runs list shows:

run ID
status icon
trigger type
started time
error message preview, when a run failed
status badge

Statuses include queued, running, succeeded, failed, and cancelled. Running and queued runs refresh while they are still active.

Read the Runs List

Select a run row to open the detail page. Use the pagination controls when the workflow has more than one page of runs.

Use the list to answer quick questions:

Did the workflow run?
Which trigger started it?
Did it succeed or fail?
When did it start?
Is there an obvious error message?

Review Run Detail

The run detail page shows the execution trace and metadata.

Top summary:

run ID
run status
trigger type
started time
finished time
duration
number of steps

Step trace:

step number
step status
node type and node ID
started and finished time
attempt number
step-specific insight, such as condition result, delay schedule, or foreach item count
input JSON, when available
output JSON, when available
step error message, when a step failed

Side panel:

run ID
status
trigger type
triggered by
created time
run-level error
context JSON, when the run has context data

Cancel an Active Run

If a run is queued or running, the detail page shows Cancel. Use this when a run is no longer needed, was started accidentally, or is waiting on bad input. Cancelled runs remain in history.

Cancel carefully when the workflow may already have completed earlier steps. Review step history before assuming cancellation prevented every side effect.

Failures usually come from missing permissions, invalid record data, disconnected integrations, changed field names, or a provider/API error. Fix the cause before retrying or enabling the workflow broadly.

Troubleshooting order:

Read the run-level error.
Find the first failed step.
Expand the failed step input and output.
Check whether the expected record, variable, integration, or permission is missing.
Fix the workflow, connected app, or source record.
Run a test from the builder before publishing broadly again.

Empty Run History

If the runs page is empty, confirm the workflow has been saved and published. Manual runs, schedules, and webhooks execute the published version, not an unsaved draft.

Retry Safety

Before retrying or triggering another run, check whether the failed run already created tasks, comments, emails, invoices, files, or external app records. Clean up duplicates or adjust the workflow first.

For customer-facing workflows, rerun with one safe record before enabling normal traffic again.

First Live Run Review

After publishing a new workflow, review the first live run even if it succeeds. Confirm the trigger record, conditions, created records, notifications, delays, and external app actions match the intended process. A successful run can still use the wrong owner, message, status, or linked record.

For high-volume workflows, keep the workflow owner watching runs during the first active period.

Workflow Runs