GitHub Pages workflow stuck queued with zero jobs; force-cancel returns HTTP 409

[Timrocketsman]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Repository: https://github.com/Timrocketsman/ai-recruiter
Affected run: https://github.com/Timrocketsman/ai-recruiter/actions/runs/42293924820
Commit: 3f344daf43c761e689a5f19824910882fb1c8765

I am looking for a supported recovery procedure for an inconsistent Actions/Pages workflow state.

Observed facts, UTC:

• A Pages deployment for the same commit, run 42295850108, failed on 2026-11-06 at 21:31:04. Its deployment log reached finished_file_sync and then a 600000 ms timeout.
• After one failed-job retry on run 42293924820, the UI showed a second queued attempt. REST continued to return queued, conclusion=null, run_attempt=1. Latest-attempt jobs were empty; attempts/2 returned 404.
• Normal UI cancellation was rejected as not in progress. One force-cancel request returned HTTP 409. The original normal API cancellation response was not retained, so I am not asserting its status code.
• Fresh public REST GETs with unique query parameters and Cache-Control: no-cache on 2026-11-07 at 05:12 UTC still showed queued/null/attempt 1 and zero latest jobs. updated_at remained 2026-11-06T21:20:36Z.
• Additional deployment requests have been stopped. Run history, logs, repository contents and Pages settings have been preserved.

The troubleshooting documentation describes queued runs with no jobs and cancellation returning 409, and directs affected users to Support:
https://docs.github.com/en/actions/how-tos/troubleshoot-workflows#canceling-workflows

Support's virtual assistant directed this account to Community and other self-service resources and said the ticket would be closed. A clarification requesting technical triage has been sent; no recovery has been confirmed.

Is there a supported way to reconcile this run/check-suite state without deleting run history or recreating the Pages site? If provider-side intervention is required, which escalation route is available for this public repository?

No credentials, private support correspondence, customer information or server access details are attached.

[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. ⭐