Environment
gh-aw-actions-release — deployment 6896879941 ended in state error (ref main, sha 382f4b0), created by @pelikhan.
Summary
The Release run was cancelled while the sync_actions job (which targets this environment) was in progress. The deployment went waiting at 22:34:43Z, then error at 22:57:25Z, which matches the run being cancelled at 22:57:24Z. The cause is a cancellation, not a code or build failure. No failed steps were found in any job.
Likely causes (not confirmed from available data):
- A manual cancel of the run.
- A concurrency group cancel by a newer run.
- Environment protection or approval timing out. The job sat about 23 minutes between the
waiting status and cancellation.
Evidence
- Succeeded:
Pre-activation, Activation, validate_container_pins, config, push_tag, defender, Conclusion.
- Cancelled:
sync_actions, release, Agent, Safe outputs, Evaluations, comment_release_prs, Push evaluations state.
gh run view --log-failed returned no failed-step logs.
- Impact:
push_tag succeeded but sync_actions and release did not, so the release may be partial.
Suggested remediation
- Check whether the tag from
push_tag exists without a matching release or actions sync.
- Confirm who or what cancelled run 37540124998 (audit log, concurrency settings in
release.yml).
- Check the
gh-aw-actions-release environment protection rules and reviewer approvals for a stall.
- Re-run the
Release workflow, or clean up the partial tag first if needed.
Generated by 🚨 Deployment Incident Monitor · copilot · auto · 13.6 AIC · ⌖ 7.77 AIC · ⊞ 6K · ◷
Environment
gh-aw-actions-release— deployment6896879941ended in stateerror(refmain, sha382f4b0), created by@pelikhan.Release,workflow_dispatch)Summary
The
Releaserun was cancelled while thesync_actionsjob (which targets this environment) was in progress. The deployment wentwaitingat 22:34:43Z, thenerrorat 22:57:25Z, which matches the run being cancelled at 22:57:24Z. The cause is a cancellation, not a code or build failure. No failed steps were found in any job.Likely causes (not confirmed from available data):
waitingstatus and cancellation.Evidence
Pre-activation,Activation,validate_container_pins,config,push_tag,defender,Conclusion.sync_actions,release,Agent,Safe outputs,Evaluations,comment_release_prs,Push evaluations state.gh run view --log-failedreturned no failed-step logs.push_tagsucceeded butsync_actionsandreleasedid not, so the release may be partial.Suggested remediation
push_tagexists without a matching release or actions sync.release.yml).gh-aw-actions-releaseenvironment protection rules and reviewer approvals for a stall.Releaseworkflow, or clean up the partial tag first if needed.