Overview
An execution is a single run of a workflow version. Each execution has a unique ID and tracks the state of every task in the workflow. Executions are created when you trigger a workflow manually or via a trigger.Execution states
Executions progress through several states:- Pending – Queued but not yet started
- Running – One or more tasks are in progress
- Succeeded – All tasks completed successfully
- Failed – One or more tasks failed
- Canceled – The execution was stopped by a user
Monitoring executions
You can list executions for a workflow or workflow version, optionally filtering by status or time range. For each execution, you can retrieve detailed status including per-task progress, input and output data, and error information when tasks fail.For a failed, timed out, or terminated execution, retry the tasks that did not finish. See Retrying executions.
Canceling executions
Cancel sets the execution toTERMINATED and stops new tasks from starting. Tasks that are already running are marked CANCELED. Work already in progress continues. Cancel a running transformation separately with the transformations cancel operation.
Retrying executions
Retry restarts a failed, timed out, or terminated execution from the tasks that did not finish. It retries tasks inCANCELED, FAILED, FAILED_WITH_TERMINAL_ERROR, or TIMED_OUT. Optional tasks are not retried.
When a failure is inside a subworkflow or a dynamic task, only the nested tasks that failed are retried. The container task is not retried. A task that has already used its retry limit is allowed one more attempt per retry request. The retry count is not reset to zero.
Complete an async task
For a task withisAsyncComplete set to true, set the status when the external work finishes:
COMPLETEDcontinues the execution.FAILEDretries the task according to itsretriessetting.FAILED_WITH_TERMINAL_ERRORdoes not retry the task.
output, it is merged with the task’s existing output.