[2026-07-13] Incident Thread

[github-actions[bot]]

❗ An incident has been declared:

Actions runs are experiencing failures to start

Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page.

[github-actions[bot]]

Incident Resolved

This incident has been resolved.

[Mr-Nilarnab]

Hi GitHub Team,

Thank you for the update and for resolving the incident.

For anyone who may still experience issues after the incident has been marked as resolved, it may be helpful to:

• Retry any failed workflow runs instead of assuming they'll resume automatically.
• Check whether self-hosted runners or repository-specific settings are contributing to the issue.
• Compare the timestamps of failed runs with the incident timeline to determine whether the failures were related to this outage.

Appreciate the quick response from the GitHub team.

[github-actions[bot]]

Incident Summary

On July 13, 2026, between 13:11 and 13:53 UTC, some customers experienced failures starting and running GitHub Actions workflows, which also affected Copilot cloud agent sessions and GitHub Pages builds since they depend on Actions. During the peak of the incident, 30% of Actions jobs failed to start and 2% were delayed more than 5 minutes.

The incident was triggered by a configuration change in an internal autoscaling component that contained outdated capacity threshold values. This caused a critical Actions service to scale below its required baseline, reducing capacity for workflow processing. We identified the regression, rolled back the change, and restored service capacity. New workflow executions recovered by 13:39 UTC. Full recovery was reached by 13:53 UTC after the queued backlog was drained.

To prevent recurrence, we have added deployment guardrails to validate that autoscaling inputs are current and to detect drift between planned and live scaling state before autoscaling changes are applied.