Pages run #717 stuck waiting; force-cancel 409 blocks site publication

[yaoshengmarketing-prog]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Repository and impact

Public repository: https://github.com/yaoshengmarketing-prog/101
Stuck workflow: https://github.com/yaoshengmarketing-prog/101/actions/runs/42670150004 (site-pages #717). Created 2026-11-09 at 18:00:52 UTC. Its deploy job 129344221940 remains waiting for github-pages deployment approval. The environment has only a main branch policy and no required reviewers. GET pending_deployments returns current_user_can_approve: false, reviewers: [].

The site-pages and football-data workflows share concurrency group site-pages-deploy. https://github.com/yaoshengmarketing-prog/101/actions/runs/42773653365 (football-data #149) is pending and says it is waiting for #717. Recent scheduled football runs were cancelled, and the last public football snapshot has expired.

Attempts to clear this single run

• GitHub UI Cancel workflow returned “Failed to cancel workflow.”
• On 2026-11-10 at 08:22:34 UTC, POST /actions/runs/42670150004/force-cancel returned HTTP 409: Cannot cancel a workflow run that has not been queued yet. Request ID: D1E1:0C30:34A4C5:504717:6AF2D44A.
• On 2026-11-10 at 08:27:05 UTC, rejecting the github-pages pending deployment returned HTTP 422: No pending deployment requests to approve or reject. Request ID: D67F:56E59:E89525:16D8B0F:6AF2D558.

GitHub Actions troubleshooting docs describe cancellation failures with 409 and a stuck concurrency group as a possible abnormal run or check suite state. Could GitHub staff clear or repair #717 so the existing workflows can resume? We are not changing environment protection, workflow configuration, or scheduling.

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

[mzain2004]

Run #717 is in a corrupted state (waiting on a deployment that doesn't exist), so only GitHub can truly clear it. But you can unblock everything yourself:

1. Try gh run delete 42670150004 (or DELETE /actions/runs/42670150004). Sometimes works when cancel returns 409.
2. If that fails, rename the shared concurrency group in both workflows (e.g. site-pages-deploy-v2). New runs stop queueing behind #717. This doesn't touch environment protection or schedules.
3. Trigger football-data manually with gh workflow run to rebuild the expired snapshot.
4. File a GitHub Support ticket with the run/job IDs, both request IDs, and timestamps asking them to clear the abnormal run state. Discussions are mostly community-answered, so staff may not see it there.

[yaoshengmarketing-prog]

Current status update (2026-11-10)

The repository is https://github.com/yaoshengmarketing-prog/101. PR #86 has been merged to separate football data production from Pages publication. football-data #150 completed successfully (and #151 also completed successfully). The older football-data #149 is cancelled.

The remaining problem is website publication. site-pages #761 was waiting but has since been cancelled. The current site-pages #762 explicitly says it is waiting for site-pages #717 to finish. #717 is still waiting (created 2026-11-09 18:00:52 UTC).

The earlier official force-cancel attempt on #717 at 2026-11-10 08:22:34 UTC returned HTTP 409, Cannot cancel a workflow run that has not been queued yet. Request ID D1E1:0C30:34A4C5:504717:6AF2D44A. GitHub UI cancellation also failed. Could GitHub staff please clear or repair only #717 so the existing site-pages publication can proceed?

[kittimzhe]

Live-checked, and the picture has moved since you posted:

• Run 42670150004 is now completed / cancelled (updated Nov 10 18:18:51) — the stuck wait is over one way or another.
• Two newer site-pages runs completed successfully today (Nov 11, 13:30 and 13:45 UTC). Your publishing pipeline is flowing again; check the live site against the latest deployment.

On the "waiting for github-pages deployment approval" mechanism, for future reference — that wait is controlled by environment protection rules, not the workflow: Settings → Environments → github-pages → if "Required reviewers" is configured, every deployment pauses for an approval click from a listed reviewer (and if the rule exists but the reviewer list is empty/broken, it waits forever — that's the wedged variant of this family). If you hit it again with no rule configured, that's a genuine stuck-deployment case like this one was.

One cleanup note: a cancelled run counts as completed for deletion purposes, so 42670150004 can be DELETEd right now — no two-week wait applies: gh api -X DELETE repos/yaoshengmarketing-prog/101/actions/runs/42670150004.