Workflow Run History

Use execution logs and node snapshots to diagnose workflows and control production behavior.

Workflow run history records executions of your AI Agent Workflows workflows. Use it to see whether a run is queued, running, successful, failed, or partial, and to open the node log when you need to investigate an outcome. Runs can be created by live triggers, incoming webhooks, or Run now in the workflow editor.

What you can review

Open Agent Workflows → Runs to browse the most recent executions across workflows. The list includes each run’s ID, workflow, status, attempt number, start time, and duration. Filter by workflow or use the status views to narrow the list.

Screenshot to add: [Runs history list]

Open a run to review its workflow, status, attempt, start and finish times, duration, and any saved trigger payload. The Node log shows each recorded node’s status, duration, message, and expandable Input and Output details where available. These records help you find where a workflow failed or where a downstream node received unexpected data.

Understand run statuses

  • Queued: The run is waiting for background execution or a scheduled retry.
  • Running: The workflow is being processed.
  • Success: The run finished successfully.
  • Failed: The run did not complete successfully and no nodes succeeded.
  • Partial: Some nodes succeeded, but the run did not finish fully successfully.

Run status and node status are different. A node log can show Success, Error, or Skipped. Read the run status together with the node messages and outputs instead of relying on one status alone.

Background retries and history retention

When background execution is enabled, some failed or partial runs may be retried automatically if the recorded error looks temporary, such as a timeout, rate limit, or upstream server error. A retry creates a separate queued run linked to the previous attempt; it does not resume from the failed node. Earlier successful nodes may run again. Manual Re-run also creates a new run, using the original trigger payload when one was recorded.

By default, the plugin keeps finished run history for 14 days. Open Agent Workflows → Settings → Logging & Retention to change the retention period or use Purge Now. Setting the period to 0 keeps finished history indefinitely. Automatic cleanup removes old finished runs and their node logs; queued or running records are not selected by that cleanup.

Detailed guides

Use these guides to investigate an execution: