GitHub Pages deployment stuck in deployment_queued and times out despite low Actions usage

[zaidbren]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Actions Runner

Discussion Details

I’m experiencing a recurring issue with GitHub Pages deployments using the official pages-build-deployment / actions/deploy-pages workflow.

This setup has worked reliably for me many times in the past with no changes to the workflow or repository configuration. However, recently, deployments consistently get stuck in a queued state and then fail automatically due to a timeout.

What happens

The build job completes successfully

The deploy job enters deployment_queued

Logs repeatedly show:

Current status: deployment_queued
Getting Pages deployment status...

After several minutes, the job fails with:

Error: Timeout reached, aborting!
Canceling Pages deployment...
Canceled deployment with ID

Additional details

Actions usage is very low (e.g., ~27 total minutes this month)

Runner type: GitHub-hosted (ubuntu-latest)

Repository permissions and Pages settings are correctly configured

Pages source is set to GitHub Actions

This occurs even with minimal, default Pages workflows

Expected behavior

The Pages deployment should proceed once the build completes, as it did previously.

Actual behavior

The deployment remains queued indefinitely and is canceled due to timeout, suggesting that no Pages runner is being allocated.

Notes

This appears to be related to GitHub Pages infrastructure availability or runner allocation rather than workflow configuration, as:

No quota limits are reached

Re-running sometimes works but often fails again

Switching to branch-based Pages deployment avoids the issue entirely

I’d appreciate clarification on whether there is a current limitation, throttling, or infrastructure issue affecting GitHub Pages deployments via Actions.

[hitem]

Same happening here. Well under the free tier but my actions keep on failing/timing out. This started a few days ago (once or twice a day), but last few hours it has been every hour.

[KubaO]

Same here.

[Uzy777]

same here. 🤣

[ai-bearing]

I have also encountered this issue.

[guocity]

its working now

[vik0t0r]

same here

[rrdevries]

Same here! It's working again, just tried a new commit and everything went smoothly.

[theodorejb]

I'm also experiencing this, except the current status is always shown as blank. The build and report-build-status jobs complete successfully, but then the deploy job shows the following:

▸ Run actions/deploy-pages@v4
Fetching artifact metadata for "github-pages" in this workflow run
Found 1 artifact(s)
Creating Pages deployment with payload:
{ ... }
Created deployment for ***23af91b, ID: ***23af91b
Getting Pages deployment status...
Current status:
Getting Pages deployment status...
Current status:

The last two lines then repeat over and over for 10 minutes, until the job fails with:

Getting Pages deployment status...
Current status:
Error: Timeout reached, aborting!
Error: Timeout reached, aborting!
Canceling Pages deployment...
Canceled deployment with ID ***23af91b

I've tried re-running the job a few times, but it fails again the same way each time.

[theodorejb]

Update: pushing a new commit to the gh-pages branch resolved the issue for me.

[AxelRICHARD]

same here!