GitHub Pages deployment workflows stuck in Queued status – unexpected error

[viva-usa-now]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Hello,

I need help with a GitHub Actions issue in my repository:

Repository: https://github.com/viva-usa-now/viva-usa

My two GitHub Pages deployment workflows are stuck in the Queued status and have not started:

• Run #69: https://github.com/viva-usa-now/viva-usa/actions/runs/43095361709
• Run #70: https://github.com/viva-usa-now/viva-usa/actions/runs/43095685834

Both runs show Queued status, and no jobs have started.

When I open one of the runs, GitHub displays this error:

"An unexpected error has occurred and we've been automatically notified. Errors are sometimes temporary, so please try again."

Previous deployments worked successfully. However, my website is not receiving the latest updates.

Could someone help me understand why these workflows are stuck and how I can restore GitHub Pages deployments?

Thank you!

Request ID: 3e2161f0-de0f-11f1-873f-1ddd5707a4b3

[erkangcmn]

Hey, I don't think anything is wrong with your repo. Your two stuck runs got caught in a GitHub incident.

Runs #69 and #70 were created at 20:19 and 20:22 UTC on Nov 11. Right around then GitHub had an incident affecting Actions and Pages ("Impact across multiple GitHub products including Actions, Pages, and Copilot products", you can see it at https://www.githubstatus.com/history). It's resolved now, but runs that got queued during an incident sometimes never get picked up. They just sit in "Queued" and show that "unexpected error" page when you open them. All your earlier pages-build-deployment runs that evening succeeded, so your setup is fine.

The incident also left your Pages site in an errored state, so you need a fresh build:

1. Cancel the stuck runs. Use the "Cancel workflow" button, or the CLI if the button doesn't work:

   gh run cancel 43095361709 -R viva-usa-now/viva-usa
   gh run cancel 43095685834 -R viva-usa-now/viva-usa

   (add --force if they still won't cancel)

2. Trigger a new Pages build. Since you deploy from main / root, any push works. An empty commit is enough:

   git commit --allow-empty -m "Trigger GitHub Pages rebuild"
   git push

   Or without a commit:

   gh api -X POST repos/viva-usa-now/viva-usa/pages/builds

3. Check that the new run finishes and that Settings → Pages shows the site as live again.

If new runs also get stuck in Queued, check githubstatus.com first. If there's no active incident, open a ticket at https://support.github.com with the run IDs and your request ID (3e2161f0-de0f-11f1-873f-1ddd5707a4b3) so they can clear the stuck runs on their end.

If this fixes it, mark it as the answer so others can find it too 👍

[erkangcmn]

Looks like your Pages builds are going through again (the new runs today all succeeded) 🎉 If this fixed it, could you mark it as the answer? Helps others with the same stuck-queue issue find it.