GitHub Copilot incident

[Retroactive] Actions workflow run failures after deployment gate approvals

Minor Resolved Upstream link ↗

Started

October 1, 2026 at 02:00 AM UTC

Duration

0 min

Resolved

October 1, 2026 at 02:00 AM UTC

Updates timeline

  1. 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 completed to avoid repeating changes.

Get an email the next time GitHub Copilot goes down

Outage alerts for GitHub Copilot, straight to your inbox. No account needed, unsubscribe in every email.

Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.

Live GitHub Copilot status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader