Executions
Understand execution runs — how patterns execute, log, and report results.
What is an execution?
An execution is a single run of a deployed pattern, from the moment a trigger fires to the moment the pattern completes or encounters an error. Every time a webhook receives a request, a schedule fires, or another pattern makes a call, DRAGOPS creates a new execution.
Execution lifecycle
Each execution moves through a series of states:
| Status | Meaning |
|---|---|
| Running | The pattern is actively executing nodes |
| Completed | The pattern finished successfully |
| Failed | The pattern encountered an unrecoverable error |
| Timeout | The pattern exceeded its maximum execution time |
| Dead letter | The pattern failed after exhausting all retry attempts |
Most executions complete in milliseconds to seconds. Long-running patterns (HTTP calls to slow APIs, large data processing) may take longer.
Execution logs
Every execution produces a timestamped log — a node-by-node record of what happened during the run. Each log entry includes:
- Timestamp — when the node executed
- Node name — which node produced the entry
- Output — the data or message the node generated
Logs are invaluable for debugging. If an execution fails, the log shows you exactly which node encountered the error and what data it was processing at the time.
Triggered by
Each execution records how it was triggered:
| Source | Description |
|---|---|
| Webhook | An HTTP request hit the pattern's webhook URL |
| Schedule | A cron schedule fired |
| Pattern call | Another pattern called this one via Call Pattern |
| Manual | You selected Run or Execute from the editor or dashboard |
Viewing execution history
Go to the Deployments page in the dashboard and select a deployment to see its execution history. Each row shows the status, trigger source, start time, and duration. Select any execution to view its full log.
Test mode vs live mode
Test mode lets you execute a pattern from the editor without deploying it. This is useful for verifying behavior during development. Test executions appear in the execution history with a manual trigger source.
Live mode is the normal state of a deployed pattern. Triggers fire automatically and executions are recorded for monitoring and auditing.
Sub-executions
When a pattern calls another pattern using the Call Pattern node, the called pattern creates a sub-execution. Sub-executions are linked to their parent execution, so you can trace the full call chain from a single entry point.
Related concepts
- Patterns — the workflows that produce executions
- Deployments — executions run on deployed patterns
- Triggers — what starts each execution