Reference
Limits and queue
What counts as one protection, how the daily limit of each plan renews, how the priority queue differs, and what happens when you reach the limit.
Every plan has a daily protection limit. One protection is one run on one file, however many functions in it you protect.
Limits by plan
| Plan | Protections per day | Queue | API access |
|---|---|---|---|
| Build | 5 | Standard | No |
| Release | 10 | Standard | No |
| Pipeline | 30 | Priority | Yes |
| Foundry | 50 | Priority | Yes |
Prices and the full plan comparison are on the pricing page.
What uses the limit
- Uses it: every job that reached processing, including one that failed because of the program.
- Does not use it: a job rejected while checking the file, symbols or settings, downloading a result again, or deleting a file.
Renewal
The limit works in a 24-hour window. The window starts with your first protection, and after 24 hours the limit is back to its full value. Unused protections do not carry over to the next window. The panel shows how many protections are left and when the limit renews, and the API returns both from GET /limits.
Queue
Jobs are processed in the order they arrive. Jobs in the priority queue, available on Pipeline and Foundry, go ahead of jobs in the standard queue. The panel and the API show a job’s position while it waits.
When you reach the limit
The panel does not let you start another protection until the limit renews. The API responds with 429 and a Retry-After header giving the seconds until renewal. Moving to a higher plan raises the limit immediately.