Help centre · Managing
How many runs does my subscription include?
The monthly allowance, what counts against it, when it resets, and what the concurrency limit does instead.
Your plan includes a number of runs per subscription period. The gauge at the top of the home page shows what you have used, what is left, and the reset date.
What counts against it?
Any run a worker actually started — a launch, a resume, a relaunch after answering a question. Each is a full execution of the pipeline.
Not counted:
- a run cancelled while still queued: nothing ever ran;
- a run interrupted by an incident on our side (category infrastructure): that is our outage, not your consumption.
When does the counter reset?
On your subscription's anniversary day, not the 1st of the month. A subscription started on the 12th resets on the 12th of each month. If that day does not exist in a given month — a 31st in February — the reset falls on the last day of that month, then returns to its usual day the month after.
What happens when the allowance is used up?
The launch is refused, with the exact count and the reset date. It is not queued: a run that would never start without telling you why is far more confusing than a clear refusal.
You can wait for the reset, or move to a higher plan — the new allowance applies immediately.
What about the concurrent-run limit?
That is a different thing. The monthly allowance is what you buy; concurrent runs are a capacity limit shared between customers. Reaching it costs nothing extra, it simply makes your next runs wait in your own queue.
You can lower that limit in Pipeline → Execution — to spread the load, for instance — but never raise it past what your plan provides.
Does a dry run count?
Yes. A dry run executes the whole pipeline, model calls included; only writing to your repository is suppressed.