All PRs stuck on "queued for work"

[cmorganmcp]

Select Topic Area

Question

Copilot Feature Area

Copilot Coding Agent

Body

All of my PRs have been stuck on "queued for work" since yesterday and copilot won't actually do any tasks. Some of them have been queued for over 18 hours. I've check all permissions and settings and can't find anything wrong. I've been using copilot without issue for weeks. Currently, copilot won't actually perform work in any of my repos. Anyone else having this issue?

[AryanKumar-108]

What You Can Try

Here’s a breakdown of troubleshooting steps recommended by fellow users and GitHub discussions:

1. Verify Copilot Agent & GitHub Actions Setups

• Ensure Copilot Coding Agent is enabled for your account and the specific repository.

• Confirm that GitHub Actions are enabled and functional—Copilot relies on those runners to process tasks.GitHub

2. Review Repository Access

• If your repos are part of an organization, double-check with the admin that Copilot policies and permissions are correctly configured.

• In personal projects, make sure the Copilot GitHub App has access via Settings → Applications → Authorized OAuth Apps.GitHub

3. Try Re-triggering the Agent

• Reassign the issue or simply close and reopen the pull request. This can sometimes jump-start the stalled task.GitHub

4. Check for Backend Delays or Glitches

• Note that while the agent is asynchronous and some delay is expected, over 18 hours in a queued state is not normal. Report the issue if there’s no progress.GitHub

• GitHub occasionally suffers Service or runner-side delays. It can help to check the GitHub Status page for any outages.

5. Engage With Feedback Threads

• Upvote or comment on the existing GitHub discussion (e.g., issue All PRs stuck on "queued for work" #172939) so GitHub support can prioritize it.

• You can also follow or open new feedback discussions in Copilot Conversations or Copilot Agent Mode categories for updates.GitHub+1

---

Summary Table

Step | Action -- | -- Check Agent & Actions | Ensure Copilot Agent and GitHub Actions are enabled for your repos. Verify Permissions | Confirm Copilot access and appropriate org/repo-level permissions. Re-trigger Agent | Close + reopen PR or reassign tasks to restart action. Check GitHub Status | See if there are broader performance issues or outages. Report & Follow Up | Upvote/comment on existing issues; raise a new one if needed.

---

TL;DR

• The “queued for work” issue with Copilot Agent is a known problem affecting multiple users.

• Verify settings, permissions, and GitHub Actions status.

• Try small triggers like closing/reopening PRs.

• If it persists, raise visibility by engaging with the relevant GitHub discussions or reporting to support.

Let me know if you’d like help drafting a support message or navigating the discussions!

---

Additional Feedback Thread

• A related yet slightly different thread on September 3 (Issue Copilot Agent Pull Request Stuck in "Queued" State #172112) describes a Copilot Agent PR stuck in “Queued” after moving the repo to a personal environment. It remains unanswered.GitHub

What You Can Try

Here’s a breakdown of troubleshooting steps recommended by fellow users and GitHub discussions:

1. Verify Copilot Agent & GitHub Actions Setups

Ensure Copilot Coding Agent is enabled for your account and the specific repository.

Confirm that GitHub Actions are enabled and functional—Copilot relies on those runners to process tasks.
GitHub

2. Review Repository Access

If your repos are part of an organization, double-check with the admin that Copilot policies and permissions are correctly configured.

In personal projects, make sure the Copilot GitHub App has access via Settings → Applications → Authorized OAuth Apps.
GitHub

3. Try Re-triggering the Agent

Reassign the issue or simply close and reopen the pull request. This can sometimes jump-start the stalled task.
GitHub

4. Check for Backend Delays or Glitches

Note that while the agent is asynchronous and some delay is expected, over 18 hours in a queued state is not normal. Report the issue if there’s no progress.
GitHub

GitHub occasionally suffers Service or runner-side delays. It can help to check the GitHub Status
page for any outages.

5. Engage With Feedback Threads

Upvote or comment on the existing GitHub discussion (e.g., issue #172939) so GitHub support can prioritize it.

You can also follow or open new feedback discussions in Copilot Conversations or Copilot Agent Mode categories for updates.
GitHub
+1

Summary Table
Step Action
Check Agent & Actions Ensure Copilot Agent and GitHub Actions are enabled for your repos.
Verify Permissions Confirm Copilot access and appropriate org/repo-level permissions.
Re-trigger Agent Close + reopen PR or reassign tasks to restart action.
Check GitHub Status See if there are broader performance issues or outages.
Report & Follow Up Upvote/comment on existing issues; raise a new one if needed.
TL;DR

The “queued for work” issue with Copilot Agent is a known problem affecting multiple users.

Verify settings, permissions, and GitHub Actions status.

Try small triggers like closing/reopening PRs.

If it persists, raise visibility by engaging with the relevant GitHub discussions or reporting to support.

Let me know if you’d like help drafting a support message or navigating the discussions!

Additional Feedback Thread

A related yet slightly different thread on September 3 (Issue #172112) describes a Copilot Agent PR stuck in “Queued” after moving the repo to a personal environment. It remains unanswered.
GitHub

[cmorganmcp]

I've gone through all of these steps multiple times over the last two days with no luck. I've checked my person settings, repo settings, and org settings. I've disabled and re-enabled anything and everything related to copilot multiple times. Every time I check github status, it shows that everything is working as expected. Copilot within github keeps telling me to install Copilot SWE Agent and add it as a collaborator, but those aren't options. Copilot SWE Agent is authorized, but it says "Copilot SWE Agent has not been installed on any accounts you have access to" when I click on it under github apps. Any other thoughts?