# Out of runs for the month

What happens when the allowance runs out, and how to make it last longer.

Each plan includes a number of test runs per month. Every execution counts, whether you started it by hand, a schedule fired it, a webhook triggered it, or it ran as part of a suite. When the allowance is gone, new runs are refused until the month rolls over, you buy credits, or you move up a plan.

![The Billing page showing usage this month against the plan allowance.](https://testsnag.com/images/docs/workspace/billing-and-plans-1-usage.r1.jpg)

Marked on the screenshot:
- Usage this month. When this reaches your limit, new runs are refused.
- Your current plan and what it includes.
- Changing plan or buying credits both raise the ceiling.

## Seeing where you stand

The Billing page shows usage against your limit as a progress bar, and warns before you hit the wall rather than after. The [busiest tests list in Analytics](https://testsnag.com/docs/running-tests/analytics.md) shows which tests are consuming it.

## Making the allowance go further

- Loosen aggressive schedules. Very few journeys genuinely need checking every five minutes.
- Group related tests into a suite rather than scheduling each one separately at the same frequency.
- Trigger from deployments instead of every push, so runs happen when risk actually changes.
- Retire tests nobody reads. A test that has been failing and ignored for a month is spending your allowance for nothing.

## Credits and plans

Run credits are a top-up for a busy month: they sit on top of the monthly allowance and are consumed only once it is exhausted. If you are buying credits every month, the plan is the cheaper answer. Either way, nothing is lost while you are out of runs. Tests, history, and schedules are all intact and resume automatically.