Usage and limits

A build was refused and you want to know which meter tripped, or you want to know what counts against you before it does. This page is the full list of what the platform meters and every refusal a meter can produce.

What is metered

Build dispatches. Every build the platform runs counts three ways at once:

• against a monthly total,
• against a 60-minute sliding burst window,
• against a per-trigger counter. Triggers are console, webhook, release, and api. Only console is attended; the other three run without a human watching, so their caps are what keep a looping webhook from spending your month by lunch.

AI generations. Counted per day and per month.

Sharing a preview burns nothing, because those bytes were built on your machine.

Where to see it

• Your plan's numbers live at /account/plans-and-limits, which states each cap and where you stand against it.
• Workspace consumption lives in workspace settings under usage, at /<workspace>/settings, broken down so a team can see which project is spending.

The refusals

When a meter refuses, the refusal names itself. Five names cover all of them:

Refusal	Meaning	What to do
monthly_cap	The monthly build total is spent	Wait for the month to roll, or raise the plan
burst_cap	Too many builds inside the sliding hour	Wait minutes, not days. The window slides, it does not reset
kill_switch	An operator paused dispatch platform-wide	Nothing on your side is wrong. Wait
counter_unavailable	The meter itself cannot be read	The platform refuses rather than guessing. Retry
unattributed	The dispatch names no workspace to charge	The trigger is misconfigured; re-mint its token

The last two are worth reading twice. counter_unavailable means the platform fails closed: an unreadable meter refuses the build instead of running it uncounted. unattributed means the same thing from the other side: a build that cannot be charged to anyone does not run.

When it fails

• burst_cap from a webhook storm: the per-trigger counter caught a loop. Fix the loop; the window clears itself within the hour.
• monthly_cap mid-month with a quiet team: check workspace settings, usage, for the project and trigger doing the spending.
• A refusal you cannot place: the five names above are the complete set. If the message names none of them, the failure is the build, not a meter.

Next

• Plans and limits for your numbers
• Console overview for where builds and triggers are configured
• Access tokens for the tokens that attribute api dispatches