[Retroactive] Actions workflow run failures after deployment gate approvals

What to do

• Check whether your product depends on GitHub Actions. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-10-01 11:34 UTC and 2026-10-01 02:00 UTC may need a replay.

• Subscribe to GitHub Actions's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github-actions works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub Actions 1

1. resolvedOct 1, 2026, 2:00 AM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.