[Retroactive] Actions workflow run failures after deployment gate approvals
The official title mentions GitHub Actions. Exact affected components are unconfirmed.
Started:
Last official update:
Resolved:
On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has recovered, but the lost state cannot be restored by retrying an approval. If you're affected, you can trigger a new run or contact GitHub Support with links to your stuck runs so we can unblock them. Once cleared, select "Re-run all jobs." This preserves the workflow run ID but starts a new attempt, rebuilds artifacts, and requires fresh deployment approvals. Before rerunning, check whether any deployment steps already
Read the full official incident ↗
MiniCrafts groups the provider's published notice by affected product. Unconfirmed scope stays unconfirmed. Published incident duration is not a measurement of downtime for every user.
What to do
Commit locally and push later; Actions jobs usually re-queue after recovery.
Check current product status and troubleshoot · Usage limits and reset rules
Official update timeline
- · resolved
On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has recovered, but the lost state cannot be restored by retrying an approval. If you're affected, you can trigger a new run or contact GitHub Support with links to your stuck runs so we can unblock them. Once cleared, select "Re-run all jobs." This preserves the workflow run ID but starts a new attempt, rebuilds artifacts, and requires fresh deployment approvals. Before rerunning, check whether any deployment steps already