Credit or package limit errors explained
What credit and package-limit errors mean in RankWatch: exhausted credits vs package limits vs seats/trackings/competitors caps.
RankWatch can block an action for two different reasons: you are out of credits, or your package feature / numeric limit does not allow it. Both can appear as “limit” errors but fix differently.
What it is
An explanation of credit balance errors vs package / quota errors.
Common causes
- Credit balance exhausted — Rank checks, rechecks, AI jobs, or tools cannot run until credits replenish or the plan changes.
- Feature gate — Package lacks a feature flag (for example AI Visibility, a workspace tool). UI may hide the nav or show “not included.”
- Numeric caps — Projects, trackings/keywords, members/seats, AI prompts, competitors exceeded.
- Workspace vs org scope — Limits are org-level; one hot client workspace can consume the shared pool.
- Permission confusion — permission denied is RBAC, not billing — see invite/permission troubleshooting.
Where to check
- Organization settings → Billing / Package (owners)
- Project and org usage views for what consumed credits
- Role Management if the error is actually permission denied