[2026-05-12] Incident Thread

[github-actions[bot]]

❗ An incident has been declared:

Incident with CodeQL

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.

[tanvishinde017]

A lot of users are currently seeing this due to an active CodeQL incident.

From what it looks like, this is a platform-side issue rather than something on the user’s end. When GitHub declares an incident like this, it usually means there are temporary problems with security scans, analysis jobs, or related CI processes.

If your workflow or checks are affected, the best approach is to wait for GitHub to resolve the incident. Retrying runs repeatedly usually won’t help during this time since the backend service itself is unstable.

You can also follow the incident thread or status page for real-time updates instead of rerunning workflows continuously.

[github-actions[bot]]

Update

CodeQL actions are currently experiencing delays, which may result in those actions being stuck in a pending state or having failed due to a timeout.

[BronkHonkyTonk]

🏴‍☠️Stays in state until next stages of self replication Reach balance remain cause of action loops 🏴

[github-actions[bot]]

Update

We're continuing to investigate issues with CodeQL actions workflows. We're additionally seeing delays for notifications, webhooks, and the Slack integration.

[github-actions[bot]]

Update

We've established that most delays are related to a queuing service and are working to scale out. Early signals from the scale-out are showing signs of recovery for some services. We'll provide an update when services are fully recovered.

[github-actions[bot]]

Update

Webhooks have fully recovered. Continuing to work on recovery for the other services.

[github-actions[bot]]

Update

CodeQL has fully recovered. We're continuing to work on recovery for the remaining impacted services.

[github-actions[bot]]

Update

All services have fully recovered.

[github-actions[bot]]

Incident Resolved

This incident has been resolved.

[xowex777]

Oki

[Shovanmondal63]

There is currently an incident affecting CodeQL. If you are experiencing issues related to CodeQL analysis, workflow execution, alerts, or GitHub Advanced Security features, you should subscribe to the discussion thread for official updates.

The GitHub team is actively tracking the incident, and updates will be posted in:

• the Discussion thread
• the GitHub Incident Status Page

To help keep the thread readable, avoid posting “+1” comments. Instead, use reactions or upvotes to indicate that you are also affected.

If your workflow_run listener issue started recently, there is a possibility it could be indirectly related to the ongoing Actions/CodeQL infrastructure incident, especially if workflows are not being enqueued at all.

[Philljames30]

CodeQL issues like this always slow things down, hope it gets sorted soon. Sometimes tools like Happymod feel smoother when stuff like this breaks the flow, just saying.