Docs: Actions troubleshooting covers quotas and kill switches (#137)
#121 (account quotas) and #131 (kill switches) documented both in Limits and Site administration, but a person whose job fails with one of their messages looks in the Actions troubleshooting table, which didn't list them. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016q5wwBFck8JHq14gHUM2CL
Canberk Demirci authored · GitHub committed signed1 parent 16676ebcommit cb1375a4046aeb876eecc7d9c2d5cbbf21f8b5b8Browse files
1 file changed+4−0
modifiedapps/diffinery/docs/actions/overview.md+4−0View file
| @@ -429,6 +429,10 @@ | ||
| 429 | 429 | | A pull request's `pull_request` workflows don't run | The pull request conflicts with its base, so there is no test merge commit. Resolve the conflicts. `pull_request_target` workflows still run. | |
| 430 | 430 | | `No Diffinery runner matches runs-on: <labels>. Linux (ubuntu-*) runners are hosted; anything else needs runs-on: [self-hosted, ...] and a registered runner.` | Hosted runners accept `ubuntu-*`, `linux`, `diffinery`, `diffinery-*`, `x64` and `amd64`. For other platforms, add `self-hosted` and start a runner with matching labels. See [Runners](/docs/actions/runners). | |
| 431 | 431 | | A self-hosted job stays `waiting` | No runner with all the job's labels is polling. Start `diffinery runner` with those labels. After 6 hours the job times out. | |
| 432 | +| `The job was not started: this account has used its <n> hosted minutes for this month ...` | The account that owns the repository used its monthly hosted minutes. They renew on the 1st (UTC); until then use a self-hosted runner, or ask a site administrator to raise the quota. See [Account quotas](/docs/reference/limits#account-quotas). | | |
| 433 | +| A hosted job stays queued, then fails with `The job waited 6 hours for one of this account's hosted jobs to finish, and was not started.` | The account already runs as many hosted jobs at once as its quota allows. Queued jobs start as running ones finish. See [Account quotas](/docs/reference/limits#account-quotas). | | |
| 434 | +| `The job was not started: Actions are suspended for this repository by a site administrator: <reason>.` (or `for every repository of <account>`) | A site administrator suspended Actions here. Nothing runs until they lift it, and a red banner on the Actions page shows the reason. See [Kill switches](/docs/admin/site-administration#kill-switches). | | |
| 435 | +| `The job was not started: Hosted runners are paused on this instance by a site administrator: <reason>. Self-hosted runners still work.` | Hosted compute is paused on the whole instance. Use a self-hosted runner, or re-run once it is resumed. See [Kill switches](/docs/admin/site-administration#kill-switches). | | |
| 432 | 436 | | `Could not start a runner: ...` | The job's container failed to start. Re-run the run. | |
| 433 | 437 | | `The runner stopped unexpectedly (exit code <n>).` | The job's container exited before reporting a result. Re-run the run; if it repeats, check that the job doesn't exhaust memory or disk. | |
| 434 | 438 | | `This runner is being replaced by a new version. The job keeps running for up to 13 minutes before it is cancelled, but a step the platform's stop signal ends fails.` | The platform is replacing this job's container. Deploys leave running jobs alone, so this is rare. The platform's stop signal reaches the running step as well, which then fails with "The platform stopped this step's processes while replacing the runner with a new version." Re-run the job. | |