Limits and timeouts
Jobs at once, the longest a job may run, and the monthly spending cap.
Three limits keep a stuck job or a busy day from turning into a surprise bill. Admins set them; jobs past a limit wait, they don't fail.
| Limit | Where | Default | What happens |
|---|---|---|---|
| Jobs at once | Settings → Limits | 20 | Further jobs wait in the queue until one finishes. |
| Longest job | Settings → Limits | 60 minutes | The job's machine is deleted, finished or not. |
| Monthly spending cap | Plan & billing | $50 | New jobs wait once this month's machine time reaches it. |
A workspace new to RaftRun's machines can run 4 jobs at once for its first 30 days, whatever the setting says. Write to us if you need more sooner.
Timeouts
When a job reaches its timeout-minutes, GitHub stops it, and RaftRun deletes its machine within seconds. The workspace's longest job is the outer limit: a machine is deleted then, whatever the job set, also when GitHub never reports the job finished.
jobs:
e2e:
runs-on: raft-ubuntu-24.04-4
timeout-minutes: 25
steps:
- uses: actions/checkout@v4
- run: npm run e2e Set timeout-minutes on every job, close to how long it really takes. GitHub's own default is 6 hours, and a hung test costs machine time until something stops it.
The spending cap
- It counts jobs and Docker hosts on RaftRun's machines this calendar month. The plan itself is not counted.
- When it is reached, running jobs finish and new ones wait in the queue. Raise the cap, or wait for the month to turn, and they start.
- 0 means no cap.