// troubleshooting guide · gitea
Gitea Actions Jobs Stuck in Waiting (No Matching Runner)
- Status
- Workaround available
- platforms:
- Self-hosted, Docker
- updated:
- November 16, 2026
- reports:
- 3
- Method
- how we research
RUNBOOK · gitea/actions-runner-waiting4 FIXES
// quick answer
Jobs wait forever when no online runner has the label in runs-on. Match the label to a registered runner and confirm the runner is registered to your instance.
Most likely fix: Match runs-on to a runner label
How to fix it
// try these in order, the most common fix is first
FIX 1Match runs-on to a runner label
- 01Open Site Administration > Actions > Runners (or repo Settings > Actions > Runners)
- 02Note each runner's labels
- 03Set runs-on in the workflow to one of those labels exactly
- 04Re-run the workflow
Did this fix it?FIX 2Confirm the runner is online and registered correctly
- 01Check the runner shows Idle/Online in the runners list
- 02Re-register with the correct instance URL and fresh registration token if it does not appear
- 03Restart the runner service
Did this fix it?FIX 3Debug with trace logs
- 01Run the runner with log level set to trace
- 02Look for FetchTask polling and label errors
- 03Check DNS errors when pulling images from docker.io
Did this fix it?FIX 4Check version-specific bugs
- 01Compare your Gitea version to go-gitea/gitea issue 31074
- 02Upgrade Gitea and the runner to the latest release
Did this fix it?
SANDBOX · gitea RUNS IN YOUR BROWSER
Try it: push, review, run CI and merge in a code host and cloud workspace
A hands-on Gitea-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.
Symptoms
Workflow run stays Waiting, or the Actions page says No matching online runner with label, or the runner shows Idle while pushes trigger nothing.
Why it happens
- C-01runs-on label does not match any registered runner label
- C-02Runner offline or registered to a different Gitea instance
- C-03Workflow trigger does not match the pushed branch
- C-04Runner only taking one task on some versions (Gitea issue 31074)
// this guide also covers
- gitea actions waiting for runner
- gitea runner idle not picking jobs
- no matching online runner with label gitea
Still not working?
If Gitea keeps failing, you're not alone. See every Gitea problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther Gitea errors
- Gitea SSH Permission Denied (publickey) or Connection Refused
- Gitea 500 Internal Server Error
- Gitea Reverse Proxy Wrong URLs or Redirect Loop (ROOT_URL)
- Gitea Push 413 Request Entity Too Large (LFS Upload Fails)
- Gitea Webhook Not Working (ALLOWED_HOST_LIST Error)
- Gitea Email Notifications Not Sending (SMTP Error)
- Why Is Gitea Using So Much Memory or CPU?
- Gitea Upgrade Failed or Database Is Locked