Job Not Starting

Diagnostic Checklist

1. 1

   Is the GitHub App installed on this repository?

   Go to GitHub Settings → Integrations → Applications and confirm WorkerRun is listed. If not, install it from the GitHub Marketplace.

2. 2

   Is the runner label correct?

   The runs-on value must be one of: "worker-run" (V8 isolation mode), "worker-run/instance-type=lite" (container mode — lite), or "worker-run/instance-type=basic" (container mode — basic). Common mistakes: workerrun, worker_run, WorkerRun, or using the wrong format for instance-type (e.g. instance_type, instanceType).

3. 3

   Check webhook deliveries

   Go to your GitHub App Settings → Advanced → Recent Deliveries. Look for the workflow_job event. If the delivery failed (non-2xx status), the webhook did not reach WorkerRun.

4. 4

   Is the event type supported by GitHub Actions?

   WorkerRun supports any event type that GitHub Actions supports — push, pull_request, workflow_dispatch, issues, schedule, and more. The runner does not filter by event type; it picks up any job dispatched by GitHub. If your job is not starting, the issue is likely with the workflow trigger configuration, not the event type.

5. 5

   Have you exceeded your monthly job quota?

   If you have reached your plan's monthly job limit, new jobs will be rejected. Check your current usage in the WorkerRun dashboard under Settings → Usage. Upgrade your plan or wait for the next billing cycle to resume.

6. 6

   Does the workflow YAML have valid syntax?

   Syntax errors in your workflow file can prevent GitHub from dispatching the job. Validate your YAML using the GitHub Actions workflow editor.