Actions creates no runs in ryuzcorp/celld; re-run stuck queued with zero jobs, cancel/force-cancel 409

[ryuzdev]

Repository: ryuzcorp/celld (public).

Since 2026-11-04 00:18 UTC, GitHub Actions creates no runs in this repository for any event.

• A re-run of https://github.com/ryuzcorp/celld/actions/runs/41743761606 has stayed queued with zero jobs. Cancel says the run is completed, force-cancel returns 409 "Cannot cancel a workflow re-run that has not yet queued", and delete returns 403.
• Since then, no new run has been created for pull_request synchronize, close/reopen, push to a matching branch, or a brand-new workflow file. A re-run of https://github.com/ryuzcorp/celld/actions/runs/41742468628 also sits queued with zero jobs.
• Disabling and re-enabling the workflow, and Actions for the whole repository, changed nothing.
• Actions works in other repositories of the same org (for example a workflow_dispatch in ryuzcorp/noite ran right away). githubstatus.com is all green.

This looks like the same fault as #211626 and #211797. Could staff clear the stuck run records for ryuzcorp/celld (runs 41743761606 and 41742468628) and restore run creation? Please do not re-run anything; we will push fresh commits once runs are created again.

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.

[samus-aran]

@ryuzdev Hey, this isn't something the Community team can assist with. Best place to raise a request is on our Support page.

[kittimzhe]

Live-checked just now — your situation has split into two different problems, one already resolved and one waiting on a clock:

1. The "no runs for any event" part healed on its own. The repo's run list now shows 135 runs in total, with the newest six all created Nov 5 (push and pull_request events, all completed, mostly success). Whatever wedged event-creation from Nov 4 00:18 UTC cleared within about a day. The pipeline is not wedged anymore — nothing to do there.

2. The two orphaned re-runs (41743761606, 41742468628) are a different animal. Both still sit queued with zero jobs since Nov 3–4: they never entered the scheduler, which is why cancel reports the run "completed" (nothing to stop), force-cancel 409s ("has not yet queued" is literal), and this variant does not self-heal. The DELETE 403 you're hitting is the age gate, not a permissions problem: run deletion unlocks when a run is completed or more than two weeks old — for yours that's Nov 17–18. Mark the date, DELETE then, and the queue view cleans up.