Self-hosted deployment job remains queued without a runner assignment #213288
Replies: 2 comments
|
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. |
|
|
Uh oh!
There was an error while loading. Please reload this page.
Summary
A manually dispatched deployment job in a private repository remains queued and has not been assigned to a self-hosted runner.
Observed state
workflow_dispatchon themainbranch.status=queued,runner_id=0, and an emptyrunner_name.Context
GitHub Status reported degraded Actions workflow-start times on 2026-11-16 and marked the incident resolved at 16:26 UTC: https://www.githubstatus.com/incidents/2zfqmghmg3s3 . This run was created at 17:32 UTC, after the incident was marked resolved. We have also found same-day reports of queued deployment workflows without runner assignment, but no confirmed common cause.
Questions
runner_idremains0?We have intentionally omitted the private repository name, run URL/ID, commit SHA, and exact runner label from this public post.
All reactions