Workflow Run | Glossary | DocLD

A workflow run is one execution of a workflow. When a trigger fires (or you run the workflow manually), DocLD creates a new workflow run. The run progresses through each step (e.g., parse, extract, notify); status, logs, and outputs are available in the dashboard or via the API. Failed steps may be retried; the run may complete, fail, or be aborted.

Run Lifecycle

Started — Trigger fired; run created.
Running — Steps execute in sequence (or parallel where supported).
Completed — All steps finished successfully.
Failed — A step failed and the run was not configured to continue.
Aborted — Run was manually stopped or aborted on failure.

Each run is tied to the workflow definition and may reference jobs (e.g., parse or extraction jobs) and webhook deliveries. Webhook payloads may include the workflow run ID for correlation.

Workflow runs are instances of workflows started by triggers. Jobs may be created within a run; webhooks can notify on run completion.

Frequently Asked Questions

Run Lifecycle

Started — Trigger fired; run created.
Running — Steps execute in sequence (or parallel where supported).
Completed — All steps finished successfully.
Failed — A step failed and the run was not configured to continue.
Aborted — Run was manually stopped or aborted on failure.

Each run is tied to the workflow definition and may reference jobs (e.g., parse or extraction jobs) and webhook deliveries. Webhook payloads may include the workflow run ID for correlation.

Workflow runs are instances of workflows started by triggers. Jobs may be created within a run; webhooks can notify on run completion.

Run Lifecycle

Related Concepts

Frequently Asked Questions

Run Lifecycle

Related Concepts

Frequently Asked Questions