Skip to main content

Execution statuses

Every status the product can show, in one place. For what these mean in context, see Executions.

Workflow status

StatusMeaningCan it be triggered?
DraftBeing edited.No
PublishedLive.Yes
StoppedTaken out of service.No

Execution status

StatusMeaningFinal?
PendingCreated, not started yet.No
In progressRunning.No
Pending approvalPaused at a review step.No
CompletedEvery node succeeded.Yes
Partially completedFinished, but not everything succeeded.Yes
Error handledA node failed and its failure path dealt with it.Yes
FailedA node failed with no failure path to catch it.Yes
RejectedA reviewer rejected an approval gate.Yes

Node status

StatusMeaningWhich path is taken next
PendingWaiting to run.
In progressRunning.
Awaiting approvalPaused for a human decision.
CompletedFinished successfully.Success
ApprovedA reviewer approved it.Success
FailedSomething went wrong.Failure
RejectedA reviewer rejected it.Failure
Fail path handledThe node failed and its failure path ran.Failure (taken)
Fail path ignoredThe node failed and had no failure path.None

Connection status

StatusMeaning
ActiveWorking.
PendingNot verified yet.
InactiveDisabled.
ErrorThe last attempt to use it failed.

Telling similar statuses apart

Error handled vs. failed. Both start with a node failing. Error handled means the workflow anticipated it — a failure path existed and ran. Failed means nothing caught it.

Rejected vs. failed. A rejection is a human decision, not a malfunction. It routes like a failure so you can handle it the same way, but the distinction is recorded.

Completed vs. approved (nodes). Approved is what a review node reports when a reviewer approves. It continues exactly like completed.

Fail path handled vs. ignored. Both mean the node failed. Handled means a failure path existed and ran; ignored means there was none, so that branch simply stopped.