GitHub Pages deployment stuck in queued status

[josevalinotto82-rgb]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Pages

Body

My GitHub Pages deployments are stuck in “Queued” status.

Repository:
https://github.com/josevalinotto82-rgb/vmg-sistema

Affected run:
https://github.com/josevalinotto82-rgb/vmg-sistema/actions/runs/41903782369

The initial deployment failed after a 10-minute timeout while showing “updating_pages”. After retrying, runs #359 and #360 remain queued.

When I try to cancel the older run, GitHub displays:
“Cannot cancel a workflow run that is not in progress.”

The repository contains the updated files, but the website still serves the previous version.

Could you check and unblock these deployments? Screenshot attached.

[saberssr114]

some this may good

[josevalinotto82-rgb]

Update: Run #360 failed because GitHub Pages reports deployment 7cbee8f3526b74f3a761e25c48c914893f8bbe88 (#359) is still in progress. Both runs now show “Queued”, and cancellation fails with “Cannot cancel a workflow run that is not in progress”. Could GitHub staff help clear the stuck Pages deployment?

Repository: https://github.com/josevalinotto82-rgb/vmg-sistema

[josevalinotto82-rgb]

Update: force cancellation also fails for both runs.

Run IDs:

• 41903782369
• 41906117676

Both POST /actions/runs/{run_id}/force-cancel requests return HTTP 409:
“Cannot cancel a workflow re-run that has not yet queued.”

The UI still shows both runs as “Queued”.

Request IDs:

• D5CA:0B00:3B83BD:64348E:6AEBEC9B
• CACC:3D6B46:CF9135:14F4EEF:6AEBECC6

Could GitHub staff investigate and clear the stuck Pages publishing state?

[joshua-lehmann]

We also hit the “finished deployment is still in progress” failure on 5 November in joshua-lehmann/cores3-apps. The dedicated Pages cancel endpoint rejected cancellation because the blocking deployment was already finished; a full Pages disable/re-enable did not help.

We restored the same public URL by switching from custom GitHub Actions publishing to Deploy from a branch → gh-pages → / (root), publishing the prebuilt site with .nojekyll, and allowing gh-pages in the deployment environment. Two branch-based deployments have succeeded. This may be worth testing if your source is currently GitHub Actions; it is not a guaranteed solution for every queued-run problem.

I posted the exact symptoms, failed/successful runs, and automation details here: https://github.com/orgs/community/discussions/211774#discussioncomment-19425317

Following this discussion for any upstream fix or explanation.