Plan limits, usage, and over-limit behavior
Understand how PMA measures capacity and consumption, warns near limits, and prevents plan-limit bypass without deleting existing records.
Before you begin
- Open the correct organization.
- Refresh Plan & Usage while online for current authoritative counts.
- Know whether the metric is active capacity or monthly consumption.
Interface walkthrough
These annotated interface maps describe the current PMA controls. They do not replace a real record review in your workspace.
Shows active animals, team seats, Housing, optimized media storage, Capture, automation, and other governed metrics.
Explains that only usage-increasing actions are blocked.
Imports, bulk actions, offline sync, reactivation, and direct API calls receive the same current-plan check.
Step-by-step workflow
Read the metric definition
Active-animal limits exclude archived, transferred, sold, and deceased records. Reactivation counts as a usage increase and requires an available slot.
Distinguish soft and hard limits
Informational limits report only. Soft limits warn or require review. Hard limits block only the operation that increases the resource.
Resolve an overage
Archive, remove, or consolidate eligible resources; wait for a consumption period to reset; or have an authorized plan change applied.
Retry queued work
Offline and imported actions are revalidated when synchronized or executed. A stale cached Pro screen cannot bypass the current server state.
Expected result
You can identify the exact measured resource, understand why an action was blocked, and reduce usage without losing historical data.
Safety boundaries
- Frontend controls are explanatory, not authoritative.
- Simultaneous requests use transaction-level protection.
- Essential care for existing animals must not be blocked by a collection-size downgrade.
- Creating extra accounts or organizations to abuse free allowances may be reviewed under PMA terms.
Troubleshooting
The count changed after refresh
PMA recalculated from authoritative records. Confirm archived states, team memberships, and pending changes.
An import preview fits but execution does not
Execution rechecks the current plan and current usage. Another action may have consumed capacity after preview.