---
title: "Extra Usage Cap"
description: "Organization admins can now set a hard cap on how much extra usage is allowed beyond your plan limit before Currents pauses recording new results."
canonical: "https://currents.dev/changelog/extra-usage-cap"
updated: "2026-04-16"
---

# Extra Usage Cap

2026-04-16, New (tracks: platform)

Organization admins can now set a hard cap on how much extra usage is allowed beyond your plan limit before Currents pauses recording new results.

---


Organization admins can now set a hard cap on how much extra usage is allowed beyond your plan limit before Currents pauses recording new results.

- Enable **Limit Extra Usage** in **Billing & Usage**
- Set a cap as a percentage of your plan limit (e.g. 0%, 50%, 100%)
- CI pipelines and test runners keep running — only recording pauses
- Recording resumes automatically when the usage cycle resets, the cap is raised, or the plan is upgraded
- Available now for all customers on extra usage plans

![](/img/changelog/extra-usage-cap-1.png)

Enabling extra usage cap

Previously, exceeding your plan limit meant accumulating extra usage fees with no upper bound. With the new cap, you decide the ceiling up front — set it to `0%` to stop the moment you hit your plan limit, or to `50%` to allow a buffer (for example, up to 15,000 recordings on a 10,000 plan) before recording is paused.

When the cap is reached, your tests continue to run in CI without disruption — Currents simply stops ingesting new results until the next cycle, or until you adjust the cap or upgrade the plan.

This makes budgets predictable while keeping pipelines unaffected.

- [Capping Extra Usage documentation](https://docs.currents.dev/dashboard/billing/plans-and-pricing#capping-extra-usage)
- [Billing & Usage](https://docs.currents.dev/dashboard/billing/usage-and-spend-control)