Limits and errors

Where to find your limits

Live current limits and usage are in app.norcube.com → Backup → Limits. Free-tier allowances and paid-plan ceilings are listed on the pricing page.

Backup has two main quota dimensions:

Maximum data sources per organization.
Maximum concurrent backup jobs running at once.

Hitting the max-data-sources quota fails the data-source create with 403 LIMIT_EXCEEDED. The concurrent-backups limit queues new jobs rather than failing them.

Org status

If your organization has unpaid invoices past the dunning grace period, write endpoints return 402 PAYMENT_REQUIRED. Reads continue to work. See Platform → Billing → Dunning.

Error codes

HTTP	Code	Meaning
400	`INVALID_INPUT`	Validation failed. Check the `message`.
401	`INVALID_TOKEN`	Token missing, malformed, or expired.
402	`PAYMENT_REQUIRED`	Organization is past dunning grace period.
403	`FORBIDDEN`	Authenticated but not allowed.
403	`LIMIT_EXCEEDED`	A configured limit was hit.
404	`NOT_FOUND`	Data source, policy, or attachment doesn't exist.
422	`INVALID_STATE`	Operation isn't valid in current state.
500	`INTERNAL_ERROR`	Unexpected server error.
501	`NOT_IMPLEMENTED`	The endpoint is reserved for a feature that hasn't shipped yet (e.g., restore).
503	`SERVICE_UNAVAILABLE`	Transient. Retry with backoff.

Connection test result codes

The connection test endpoint returns an errorCode field on failure:

Code	Meaning
`auth_failed`	Credentials rejected.
`timeout`	Couldn't open a TCP connection.
`tls_error`	TLS handshake failed.
`unreachable`	DNS lookup failed or host unreachable.
`server_error`	Connected, but couldn't run the verification query (usually a permissions issue on the role).

See Test the connection.

Status

Live status at status.norcube.com.