Plan limits for spinners and jobs
Every CXGear plan includes usage limits so cost and capacity stay predictable. Spinners and jobs are among the meters you will hit first when you move from a demo into daily outreach. When a limit is reached, CXGear blocks the action with a clear message — it does not fail silently.
What is limited (spinner-related)
Section titled “What is limited (spinner-related)”| Meter | What it counts |
|---|---|
| Spinners | How many non-supporting (main) spinners you can have |
| Jobs / month | How many spinner runs this calendar month |
| Records spun / month | How many rows processed this calendar month |
Supporting (child) spinners linked for retries or callbacks generally do not consume the spinner count the same way main spinners do — they are part of a parent design. Jobs and records from child runs still count toward monthly usage when they process rows.
Other plan meters (projects, seats, data tables, channels, PCA analyses) are separate; see Plans & usage and Trial limits.
Typical caps by plan
Section titled “Typical caps by plan”Always confirm live numbers on Billing → Usage. Typical values:
| Plan | Spinners | Jobs / month | Records / month |
|---|---|---|---|
| Trial | 2 | 50 | 500 |
| Pro | 25 | 500 | 10,000 |
| Advanced | 100 | 5,000 | 100,000 |
| Enterprise | Custom / unlimited | Custom / unlimited | Custom / unlimited |
Monthly counters reset at the start of each calendar month. Spinner count is a standing limit (how many main spinners exist), not a monthly reset.
src/assets/screenshots/10-billing-usage.pngWhen you hit a limit
Section titled “When you hit a limit”Examples of what you might see:
Spinner limit reached on the trial plan (2/2). Upgrade to continue.
Monthly record/spin limit reached on the pro plan (… ). Upgrade to continue.
Toasts appear above drawers and modals so you can read them while a form is open.
| Action blocked | Meter that is full |
|---|---|
| Create / publish another main spinner | Spinners |
| Start another run | Jobs / month or records / month (if the run would exceed remaining rows) |
| Large run on a big table | Records / month |
What to do
Section titled “What to do”- Open Billing and see which meter is full.
- For spinner limits: archive or remove unused main spinners if your process allows, or upgrade.
- For monthly jobs/records: wait for the calendar reset, reduce run size, or upgrade to Pro / Advanced / Enterprise.
- Prefer one well-designed parent spinner with supporting children over many near-duplicate main spinners.
Success looks like
Section titled “Success looks like”- Billing meters show headroom before a big campaign
- Runs complete without plan-limit toasts
- Team knows which plan they are on and what “records spun” means
Common problems
Section titled “Common problems”| Symptom | Likely cause | What to do |
|---|---|---|
| Cannot create a third spinner on Trial | Spinner cap is 2 | Upgrade or remove an unused spinner |
| Mid-month runs blocked | Jobs or records meter full | Upgrade or wait for reset |
| Thought child spinners “used up” the cap | Misread the meter | Check Billing; supporting spinners are excluded from the main spinner count |
| Records page empty but meter increased | Runs processed rows with failures | Check Jobs and journey errors |