Update

We are investigating reports of issues with Actions and Pages. We will continue to keep users updated on progress towards mitigation.

Could you advise how to recover already queued macOS jobs after mitigation? Our standard macos-26 and macos-26-intel jobs both report that a hosted runner was assigned but are still waiting for it to come online, with no steps started. A cancellation request was acknowledged in the UI, but that earlier run also continues to report queued in the API. The Actions budget has remaining allowance and does not show Usage blocked.

One validation run has been queued since approximately 15:35 UTC on November 4; the subsequent Intel build has the same symptom. Should these existing runs be left queued to recover automatically, or canceled and rerun once the incident is resolved? Is any account-specific action required? Private repository URLs and credentials have been omitted.

Update

We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs.

Incident Resolved

This incident has been resolved.