Troubleshooting
Provisioning, quota, and storage issues
Resolve failed creation, exhausted limits, and storage pressure.
6 minute read · Updated September 2026Validation errors
A 422 response means the request was understood but one or more values are invalid. Check the database name, supported region, plan identifier, and PostgreSQL version. The console should show the API’s field-level message.
Quota reached
- Confirm the active project in the switcher.
- Review database, storage, and connection limits in Settings or Billing.
- Remove unused temporary resources only after validating retention needs.
- Upgrade the plan when the workload genuinely needs more capacity.
Storage pressure
Investigate growth before increasing capacity. Look for oversized indexes, retained audit or event tables, unbounded logs, abandoned temporary tables, and vacuum health. Do not delete data blindly to clear an alert.
Storage exhaustion is operationally urgent
When free space is critically low, pause nonessential writes and contact support while a controlled capacity or cleanup plan is executed.
Was this guide useful?
Get helpIf anything is unclear or incorrect, tell the support team.