Executions
Inspect every durable workflow run and debug node-level failures.
What is an execution?
An execution is one run of one workflow. Manual runs and accepted webhook events create durable records. The run is queued and processed asynchronously; the editor listens for real-time status updates and also checks persisted state as a fallback.
| Status | Meaning |
|---|---|
| PENDING | The run or node has been created and is waiting to start. |
| RUNNING | Processing has started. |
| SUCCESS | The reachable workflow path completed successfully. |
| FAILED | A validation, provider, template, network, or node error stopped the run. |
Execution list controls
- Search by workflow name.
- Filter by All statuses, Pending, Running, Success, or Failed.
- Filter by one of your workflows.
- Select Refresh to reload the list and workflow options.
- Use Previous and Next to page through results.
- Select an execution card to open its detail page.
Each card shows workflow name, shortened execution ID, status, trigger, created/start/completion times in UTC, duration, and a safe error when present.
Execution details
The summary contains trigger, timestamps, duration, workflow name, full execution ID, and workflow-level error. Node execution history is shown in execution order with each node's type, ID, status, timestamps, duration, error, and—when permitted—a safe result summary.
Safe summaries
History does not return full webhook payloads, AI text, HTTP bodies, or provider secrets. It may show safe metadata such as HTTP status/content type, Gemini provider/model/token usage, Manual Trigger status, or Telegram send identifiers.
Debug a failed workflow
- Open the failed execution and find the first failed node in Node execution history.
- Read its bounded error message and identify whether it concerns settings, credentials, a template, an external provider, or a network response.
- Return to the workflow, open that node's settings, and correct the value. Verify the node is connected to every variable source it references.
- Save the workflow. For Manual Trigger, run it again. For webhooks, send a new external event.
- Open the new execution; previous execution history remains unchanged.