RunsOn: Jobs Queued Indefinitely and Webhook Delivery

RunsOn launches runners in response to GitHub webhooks. If those webhooks are not delivered to your entrypoint, jobs sit queued indefinitely with no runner.

Per RunsOn's troubleshooting docs, jobs queued indefinitely are commonly a webhook delivery problem: GitHub must deliver webhook events to your RunsOn entrypoint for runners to be launched (runs-on.com/docs/maintenance/troubleshooting). The entrypoint is the RunsOnEntryPoint URL from your CloudFormation Outputs (runs-on.com/quickstart). Verify current guidance on runs-on.com.

What is happening

GitHub sends webhook events to the RunsOn GitHub App / entrypoint when a job needs a runner.
If delivery fails, RunsOn never sees the request and no runner is launched.
The job therefore stays queued with nothing to pick it up.

How to address it (per RunsOn docs)

Check webhook delivery from GitHub to the RunsOn GitHub App and entrypoint.
Confirm the RunsOnEntryPoint URL in the CloudFormation Outputs is reachable.
Verify the GitHub App is installed and receiving events.

The managed contrast

The webhook-to-entrypoint path is infrastructure you run with RunsOn, so a delivery failure leaves jobs stuck. Latchkey advertises zero queue time on fully managed runners, and there is no self-hosted entrypoint whose webhook delivery you have to keep healthy.

Frequently asked questions

Why are my RunsOn jobs stuck queued forever?

Per RunsOn's docs, this is often a webhook delivery problem: GitHub is not reaching your RunsOn entrypoint, so no runner is launched (runs-on.com/docs/maintenance/troubleshooting). Verify current guidance on runs-on.com.

Where do these RunsOn details come from, and are they current?

Every RunsOn detail here is drawn from RunsOn's own docs and pricing pages (runs-on.com, runs-on.com/pricing, runs-on.com/docs). RunsOn's pricing, tiers, and supported runners can change, so verify current pricing and capabilities on runs-on.com before you decide. Self-reported RunsOn scale and savings figures are RunsOn's own claims and are not independently audited.