Understand Your Quotas
A hosted Stack has two quotas for simultaneous work and one quota for watched Projects. See Quotas for their definitions and plan defaults. This guide explains what the Dashboard shows and what you can do when you reach a limit.
Check Your Usage
Open Settings in the Dashboard. The Usage section shows:
- Runs in flight: the number of general slots currently in use compared with your Effective Concurrency.
- Watched Projects: the number of registered Projects compared with your watched-Projects quota.
The Concurrency section shows your General Concurrency and Interactive Reserve settings. If a plan change places a saved setting above its quota, Settings also shows the lower effective value currently in force.
The Usage section doesn't show how much of the Interactive Reserve is currently occupied. An Interactive Turn waits only when no general slot or reserved slot is available.
When Run Capacity Is Full
The Run Cap is the plan ceiling on General Concurrency. Zozo uses the lower of that quota and your setting as Effective Concurrency.
When every general slot is occupied:
- Targeted and fleet Dispatch wait for a general slot.
- An Interactive Turn can use the Interactive Reserve when a reserved slot is available.
- Waiting work receives each available general slot in the order described in How Dispatch Decides.
You don't need to reset or replenish anything. A slot becomes available as soon as work in flight ends. To allow more simultaneous work, increase General Concurrency in Settings if your Run Cap permits it.
When the Interactive Reserve Is Full
The Reserve Cap is the plan ceiling on your Interactive Reserve, which is extra capacity reserved for a person waiting on a live reply. Zozo uses the lower of that quota and your setting as the Effective Reserve.
An Interactive Turn first tries to use a general slot. It waits only when both general capacity and the Interactive Reserve are full. Targeted and fleet Dispatch continue to use general capacity only.
To keep more capacity available for live sessions, increase the Interactive Reserve in Settings if your Reserve Cap permits it. Setting it to 0 removes that additional headroom.
When a Concurrency Quota Changes
A change to the Run Cap or Reserve Cap doesn't interrupt work already in flight. Later admission decisions use the new effective value. If current usage is already above a newly lowered value, existing work finishes before more work is admitted.
Zozo preserves your saved concurrency settings after a plan downgrade. The Dashboard shows the lower effective value while the quota is lower. If the quota rises again, Zozo can use the setting you previously chose without requiring you to enter it again.
When the Watched-Projects Quota Is Full
The watched-Projects cap limits how many GitHub repositories your Stack can register as Projects.
When Watched Projects shows that you're at the quota:
- Adding another Project fails with an explanation.
- Saving an existing Project doesn't consume another place.
- Remove a Project you no longer want Zozo to watch before adding a new one.
Follow Watch a Project to manage the Projects your Stack watches.
Related
- Quotas: review each quota, its default, and where Zozo enforces it.
- Work Model: understand how work enters admission and Dispatch.
- How Dispatch Decides: see which waiting work receives the next general slot.