calling_capacity_reached
- HTTP status
- 429
- Retry
- After Retry-After
- Execution
- Nothing was done
- Admin needed
- No
Calling capacity reached. Call starts are paced. This is separate from your API rate limit: the request was valid, but no capacity was free to start the call, so nothing was dialled.
What it means
The API returns HTTP 429 with error.code set to calling_capacity_reached. The default message is: "Too many calls are being started right now. Retry after the number of seconds in the Retry-After header."
Common causes
- A burst of call starts above the pace calls can be started at.
- The workspace is already running its maximum number of simultaneous calls.
How to identify it
Check the response status (429) and error.code (calling_capacity_reached). Branch on error.code, not on the message text: messages can be reworded, codes do not change within v1. Log error.request_id (also sent as the X-Request-Id header) so support can find the request.
How to fix it
- Wait
Retry-Afterseconds and retry (with the same Idempotency-Key if you sent one). Spread call starts out, or use a campaign for volume.
Retry guidance
Wait for the number of seconds in the Retry-After response header, then retry.
Did anything happen?
This request was refused before any call was placed and before anything was charged.
Idempotency
Nothing was dialled. Retry after the wait (with the SAME key if you sent one).
Who can fix it
The developer who sends the request can fix it; no administrator action is normally needed.
When to contact support
If this happens at low volume, write to support@relationsai.com with the request_id. See Support for what to include (the request_id, the time in UTC, the operation, and whether you used a test or live key) and what never to send (API keys, Authorization headers, webhook signing secrets, recording links, transcripts or customer data).
Example error response
JSON
Operations that can return this error
POST /calls: Place a call
See all codes in the error-code reference.