Two GitHub Actions runs permanently queued with zero jobs and cannot be cancelled

[rafaeldeak-lab]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Discussion Details

Repository

https://github.com/rafaeldeak-lab/dzn-network

Workflow

Name: DZN Owner Console Preview

Workflow file:

.github/workflows/dzn-owner-console-preview.yml

Branch:

feature/event-platform-performance-foundation

Head commit:

932ec3ddbab87b49a04771efdbb949053096e0f7

Problem

Two manually dispatched GitHub Actions runs are permanently stuck in the Queued state:

1. https://github.com/rafaeldeak-lab/dzn-network/actions/runs/30345005158
2. https://github.com/rafaeldeak-lab/dzn-network/actions/runs/30355219313

Both runs have:

• zero jobs;
• no runner assigned;
• no workflow steps started;
• no artifacts;
• no deployment;
• no Cloudflare request;
• no database operation.

The first run has remained unchanged since 2026-07-28T09:04:09Z.

Cancellation failures

Trying to cancel either workflow through the GitHub website displays:

Failed to cancel workflow.

I also attempted:

• standard REST API cancellation three times;
• the documented force-cancel REST API.

Both cancellation methods returned GitHub HTTP 500.

Replacement run also became stuck

I dispatched exactly one replacement run using the same workflow, branch and concurrency group.

GitHub did not cancel or replace the original pending run. Instead, both runs remained queued with zero jobs.

No third run has been dispatched because I do not want multiple runs to unexpectedly execute later.

Concurrency configuration

concurrency:
  group: dzn-owner-console-preview-${{ github.ref }}
  cancel-in-progress: false

Evidence

The screenshots below show both workflow runs stuck in the queued state and the cancellation failure.

Requested help

Could a GitHub staff member please investigate and clear these two corrupted queued workflow-run records, clear any stuck backend concurrency state, and confirm that neither run can unexpectedly start later?

Both normal cancellation and force-cancel return GitHub HTTP 500, so I cannot clear them from my side.

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