ARCHIVED OFFICIAL INCIDENT

[Retroactive] Actions workflow run failures after deployment gate approvals

GitHub · Last saved provider status: resolved

Current service report →
This is historical evidence.

The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.

Saved event details

Provider status
resolved
Provider impact
minor
Provider record created
01 Oct 2026, 02:00:00 UTC
Provider record updated
01 Oct 2026, 11:34:33 UTC
Explicit provider start
01 Oct 2026, 11:34:16 UTC
Explicit provider end
01 Oct 2026, 02:00:00 UTC

The provider's end time precedes its start time. These reported timestamps do not establish a valid event duration.

Affected components reported by the provider

The provider explicitly listed no affected components in this saved revision.

These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.

A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.

Provider updates in saved revisions

Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.

  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.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC