Troubleshooting

A job stays queued

Why a job set to a Skipbox label waits on GitHub, how to read the reason on your account's page, and what to do for each.

Open your account's page on skipbox.dev. Recent jobs shows each job's state, and the reason when it didn't run.

Waiting

Your trial or plans are busy. The trial runs 1 job at a time, and plans run what fits in their vCPU. The job starts when a running one ends. The page says what to add to run more at once. See Concurrency and queueing.
Skipbox is getting a VM for it. Starting a VM takes a little while. If it waits longer than the page says, write to hello@skipbox.dev.
Waits for the installer to sign in. On an organization, the person who installed the app signs in to skipbox.dev once; then the job runs.
Waiting for GitHub to confirm who installed Skipbox. GitHub hasn't told Skipbox yet. The job runs once it does.
Add an email address to start your trial. Add it on the dashboard, and the job runs.

The page says	Do this
Public repository	Skipbox runs private repositories only. Set `runs-on` back to a GitHub-hosted label there
More than one size in runs-on	Keep one size label. See Labels and sizes
Needs a larger plan	Add a plan of that size, or use `skipbox`
The trial runs 4 vCPU jobs	Use `skipbox` during the trial
Trial ended, or no plan	Choose a plan. See Plans
You already used your trial	Each person gets one trial. Choose a plan
Payment still due	Update the card in Manage billing. See Billing

A refused job doesn't restart by itself. After the fix, re-run it on GitHub.

Skipbox didn't get the job. Check that:

the runs-on label is spelled as in Labels and sizes;
the app is installed on the account and may use this repository: on GitHub, open the app's Configure page and add the repository;
the repository is private.

GitHub cancels a job queued for 24 hours without a runner. Fix the reason above, then re-run it on GitHub.

Updated November 9, 2026