[2026-04-02] Incident Thread

[github-actions[bot]]

❗ An incident has been declared:

Disruption with some GitHub services

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.

[rdar-lab]

GitHub Copilot coding agent doesn't work. Could be related to github actions

[github-actions[bot]]

Update

When assigning tasks to Copilot Cloud Agent, the task will appear to be working, but may not actually be running.

We are investigating.

[awingfield916-tech]

Sounds great!

[github-actions[bot]]

Update

We are once again seeing recovery with Copilot Cloud Agent job starts.

We are keeping this open while we verify this won't recur.

[github-actions[bot]]

Update

This issue has recurred. Customers will once again experience false job starts when assigning tasks to Copilot Cloud Agent.

We are still investigating and trying to understand the pattern of degradation.

[awingfield916-tech]

Yes I would like to it sounds good.

[github-actions[bot]]

Update

Although we are observing recovery once again, we expect continued periods of degradation.

Work that is queued during times of degradation does eventually get processed.

We continue to investigate and find a mitigation, and will update again within 2 hours.

[github-actions[bot]]

Incident Resolved

This incident has been resolved.

[EH-MLS]

+1. I’m seeing the exact same "stale agent" issue with Opus failing to complete tasks. Yesterday, it was constantly throwing timeouts. Today, it seems like a band-aid was applied so it just finalizes the task at the last second with zero progress.

Honestly, it feels deliberate—like a nasty workaround to force us to burn through our Premium Requests on a broken service without throwing an explicit error. We shouldn't be losing our quota on this.

[EH-MLS]

+1. I’m seeing the exact same "stale agent" issue with Opus failing to complete tasks. Yesterday, it was constantly throwing timeouts. Today, it seems like a band-aid was applied so it just finalizes the task at the last second with zero progress.

Honestly, it feels deliberate—like a nasty workaround to force us to burn through our Premium Requests on a broken service without throwing an explicit error. We shouldn't be losing our quota on this.

[tsileo-wdi]

I'm experiencing the same issues again as earlier today. Agents don't respond when tagged on an open PR. And don't start work when assigned to an issue.

[EH-MLS]

Worse still, while the throttling used to cause flat-out timeouts, GitHub's alleged 'fix' is a joke. Now, the system just stalls and manages to spit out a completion right before the timeout limit hits—barely making any real progress. Meanwhile, Sonnet runs circles around it, doing way more in less time. This janky workaround is probably because Copilot is struggling with per-token costs, but to the user, it just exposes how unreliable the tool is and how GitHub is failing to deliver.

[awingfield916-tech]

I just look forward to making everything run smooth for everyone.

[awingfield916-tech]

I just like to make sure everything's running great for everybody
.