Orphaned Actions run queued for 26 days; cancel/force-cancel 409, delete 403

[erkancelebi06-pixel]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Discussion Details

Hello GitHub Actions team,

A workflow run in a private repository has been stuck in queued status since 2026-09-13T08:56:15Z. As verified on 2026-10-09, updated_at still equals created_at. There are zero jobs, zero check runs, and zero artifacts.

Run ID: 34748697439
Check suite ID: 94113379926

Normal cancellation and force cancellation both return HTTP 409: Cannot cancel a workflow run that has not been queued yet. Deletion returns HTTP 403: Could not delete the workflow run. The repository owner's account has admin permissions, and the classic token includes repo and workflow scopes. The run is 26 days old, beyond the documented two-week deletion threshold.

Reproduced at 13:15 UTC on 2026-10-09. Request IDs:

• cancel: CD90:102A9D:9B315C:E3365F:6AC8E8EE
• force-cancel: CD94:16A9B:9C0F0F:E6A3FE:6AC8E8F0
• delete: CD9E:1D762D:9D5E16:E703FB:6AC8E8F3

After every request, GET confirmed that the run remained unchanged. The listing says queued, while both cancellation endpoints say it has not been queued. This suggests inconsistent server-side state.

The support portal shows that my Standard account does not include technical support and offers no Actions ticket category. Could GitHub staff please investigate and remove or force-complete this exact orphaned run? I can provide the private repository URL through a private support channel if needed.

Thank you.

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