Pages deployment times out after successful build; blank deployment status and stuck queued run

[ManuManiac]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Pages

Body

My public GitHub Pages repository builds successfully, but publishing
repeatedly times out.

Repository:
https://github.com/ManuManiac/Dj_schedule

Website:
https://manumaniac.github.io/Dj_schedule/

Branch: main
Current commit:
36f09d0e1c1f76898fe366fefc81d6ffc8259149

The repository contains a small static HTML/JavaScript website.

Latest failed deployment

Run #26:
https://github.com/ManuManiac/Dj_schedule/actions/runs/41964484523

Deployment ID:
7564742779

The build and artifact upload succeeded. The github-pages artifact
was approximately 34.3 KB.

actions/deploy-pages@v5 found the artifact and created the Pages
deployment. It then repeatedly printed:

Getting Pages deployment status...
Current status:

The status after the colon remained empty.

The deploy job failed after approximately 10 minutes 32 seconds with:

Timeout reached, aborting!

After the workflow failed, the separate deployment-status endpoint
still reported in_progress:

https://api.github.com/repos/ManuManiac/Dj_schedule/deployments/7564742779/statuses

Earlier stuck run

Run #25:
https://github.com/ManuManiac/Dj_schedule/actions/runs/41960993342

This run has reported queued, but its latest jobs endpoint returned
zero jobs:

https://api.github.com/repos/ManuManiac/Dj_schedule/actions/runs/41960993342/jobs?filter=latest

Attempting normal cancellation returned:

Cannot cancel a workflow run that is not in progress.

An earlier deployment also reported:

Getting Pages deployment status failed
HttpError: Not Found

The stack trace referenced getPagesDeploymentStatus.

What I tried

• Rerunning failed jobs: the attempt stayed queued.
• Normal cancellation: rejected with the message above.
• Triggering a fresh deployment: build succeeded, but deployment
  again timed out while polling an empty status.

Could someone help investigate whether these Pages deployment
records are stuck or inconsistent, and advise how to recover
publishing without deleting the repository or changing the website?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[ZaneDaniel11]

Hi @ManuManiac , this looks like a stuck Pages deployment on GitHub's side, not a problem with your site. Your build and artifact upload worked. Polling returns an empty status, the deployment stays in_progress after the job dies, and run #25 sits in queued with zero jobs. Together those mean the Pages backend never picked up the deployment. Here are some steps to clear the stuck records and get publishing working again. None of them touch your site's content.

1. Check for an incident first
Look at https://www.githubstatus.com for any Pages or Actions incident around the time of your runs. If one is open, waiting it out and re-running may be all you need.

2. Force-cancel or delete the stuck queued run (#25)
A normal cancel fails because the run isn't technically "in progress." The force-cancel endpoint usually works when that happens:

gh api -X POST repos/ManuManiac/Dj_schedule/actions/runs/41960993342/force-cancel

If it still won't go away, delete the run:

gh run delete 41960993342 -R ManuManiac/Dj_schedule

This matters if your workflow uses concurrency: group: pages, because a ghost run can keep holding that group.

3. Mark the stuck deployment inactive, then delete it

gh api -X POST repos/ManuManiac/Dj_schedule/deployments/7564742779/statuses -f state=inactive
gh api -X DELETE repos/ManuManiac/Dj_schedule/deployments/7564742779

GitHub only lets you delete a deployment after it's inactive, which is why the status call comes first. Do the same for any other deployments on the github-pages environment that still show in_progress.

4. Reset the Pages source
Go to Settings → Pages → Build and deployment → Source. Switch it to Deploy from a branch and save, then switch it back to GitHub Actions. This often resets the Pages site's internal state. While you're there, open Settings → Environments → github-pages and make sure main is allowed under deployment branches and that there are no required reviewers or wait timers.

5. Re-run with a longer timeout
After the cleanup, trigger a fresh run. To be safe, you can raise the timeout (it's in milliseconds and defaults to 10 minutes):

- uses: actions/deploy-pages@v5
  with:
    timeout: 1200000

6. Workaround if Actions deployments keep hanging
Your site is plain static HTML/JS with no build step, so you can skip Actions entirely. Set Source → Deploy from a branch → main / (root) and Pages will serve the repo as it is. Your URL and content stay the same. You can switch back to Actions later.

7. If none of this works
Some stuck deployment records can only be cleared by GitHub staff. In that case, open a ticket at https://support.github.com and include your run IDs (41964484523 and 41960993342), deployment ID 7564742779, and commit 36f09d0. You've already collected all the details they'll ask for.

---

[ArtricX]

Same issue here since 2026-11-06 21:32 UTC on a public repo (ArtricX/ailab, Deploy from a branch: main / root).

• The build job and artifact upload succeed every time (about 142 MB).
• On the first deploy attempt of each commit, the status sits at "syncing_files" until "Timeout reached, aborting!" after 10 minutes.
• On every re-run of the same commit, the status stays empty from the start.
• A new commit (fresh deployment) failed the same way.
• Deploys worked normally until 2026-11-06 00:18 UTC.

Affected runs: 42297493443, 42308138179.
I opened a support ticket, but it was closed because the account is on the free plan.

@github staff, could someone check whether Pages file sync is stuck for some repositories? Thanks.