# Fix for queued jobs left without a runner

Source: https://sengi.run/changelog/2026-11-17-fix-for-queued-jobs-left-without-a-runner

By Sengi · Published Nov 17, 2026

## What changed?

Each queued job now gets its own runner. Before, a job could be left without one when GitHub reported it as queued after another job had already started on a runner made for it, or when GitHub sent several queued notices for one job.

## Details

GitHub hands a runner to any queued job with the matching label, and the notice that a job is queued can arrive after the job has started elsewhere. Sengi used to skip creating a runner in that case, so the job could wait a long time or be canceled. It now creates one runner per queued job again.

GitHub also sometimes sends two or three queued notices for one job. Each used to start its own runner, and on a project at its vCPU limit the extras never got a machine or expired. Now a job starts one runner however many notices arrive. Jobs held for a deployment approval are acknowledged correctly too.

## Related pages

- [Troubleshooting](https://sengi.run/docs/troubleshooting)
- [Runner sizes](https://sengi.run/docs/runner-sizes)

## More changes

- Next: [Free jobs on accounts without a card stop after 2 hours](https://sengi.run/changelog/2026-11-17-free-jobs-on-accounts-without-a-card-stop-after-2-hours) (Nov 17, 2026)
- Previous: [Fix for jobs stuck as queued after the Nov 1 clock change](https://sengi.run/changelog/2026-11-17-fix-for-jobs-stuck-as-queued-after-the-nov-1-clock-change) (Nov 17, 2026)
- [All changes in the Sengi changelog](https://sengi.run/changelog)
