Executions

An execution is one run of a flow.

What executions show

Executions make a workflow observable step by step. Use them to understand what happened during a run and where a workflow needs adjustment.

Execution details include:

• The ordered list of flow steps.
• Request inputs sent by each step.
• Response bodies, headers, and status information.
• Variables created or updated during the run.
• Failures and the step where they occurred.

Debugging a failed execution

When a run fails, start with the first failing step:

1. Check the request body and headers.
2. Confirm variables resolved to the expected values.
3. Read the response body and status.
4. Update the request, flow condition, or source data.
5. Replay with the same inputs when appropriate.

Replay

Replay is useful when a workflow failed because of an incorrect request shape, a missing variable, or a temporary downstream issue.

Before replaying, confirm whether the workflow is safe to run again. Some API operations create or mutate data and may require idempotency controls.