Stuck Releases

Learn how to identify and resolve stuck releases in Release Orchestration.

Stuck releases are releases that are not progressing. This topic helps identify and resolve them.

Identifying stuck releases

Watch for the following signs that a release is stuck.

Signs of a stuck release

• No progress: no progress for an extended period.

• Pending status: stuck.

• Waiting: waiting for dependencies.

• Blocked: blocked by approvals.

Common causes

The following issues most often cause a release to get stuck.

Dependency issues

Dependencies are not met:

• Failed dependencies: dependencies failed.

• Blocked activities: an activity is waiting on a prior activity to complete.

Approval issues

Approvals are blocking the release:

• Pending approvals: approvals are pending.

• Missing approvers: approvers are not assigned.

Resolution

Resolve the underlying dependency or approval issue so the release can proceed.

Dependency resolution

• Check status: check dependency status.

• Fix and continue: fix the underlying issue (e.g., a pipeline error) and resume execution.

• Retry or ignore: retry a failed activity or ignore it and continue (based on your process requirements).

Approval resolution

• Check approvals: check approval status.

• Assign approvers: assign approvers.

• Complete sign-off: complete the manual activity by recording inputs or sign off so the release can proceed.

Related topics

• Common issues

• Execution failures

• Variable mapping errors