Skip to main content

Run history

Every run — triggered by a test, a webhook, or a schedule — is recorded. The history is your audit trail: it answers what ran, when, and why did it fail?

What each run records​

  • The workflow and the version that ran.
  • The run's status (queued, running, success, failed) and when it finished.
  • A step for each node executed, with that node's input, output, and any error.

Using the history to debug​

When a run fails, open it and walk the steps in order. The failing step shows its error message and the exact input it received — usually enough to see whether the problem is the data, a mapping, or an external system's response.

How long history is kept​

Run history is retained for a period that depends on your plan. Higher plans keep history longer. Check your plan's limits for the exact retention window.

note

Because history is tied to the version that ran, you can tell whether a failure came from a recent change — compare the failing run's version to the one before it.