Copy page

Error codes

idempotency_key_in_progress

Request with this Idempotency-Key in progress. An earlier request with the same key has not finished yet. When it finishes, a successful (2xx) answer is stored and a retry with the same key replays it; so is an error whose documentation says its outcome is unknown and the answer is kept (for example campaign_outcome_unknown). Any other error is not stored, and the retry then runs the request again.

What it means

The API returns HTTP 409 with error.code set to idempotency_key_in_progress. The default message is: "A request with this Idempotency-Key is still being processed."

Common causes

• A client retried before the first attempt finished.
• Two workers sent the same operation concurrently.

How to identify it

Check the response status (409) and error.code (idempotency_key_in_progress). 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 for Retry-After seconds and send the identical request again with the same key.

Retry guidance

Wait for the number of seconds in the Retry-After header. For a write, read the resource first to find out whether the change was applied before you send anything again.

Did anything happen?

The work may have started before this error was returned. Do not assume nothing happened: read the resource (for a call, list calls filtered by to and created_after; for a campaign, retrieve it) before you send anything again.

Idempotency

Keep the SAME key. After Retry-After the retry replays the stored answer if the first request stored one, or runs the request if it ended in an error that is not stored.

Who can fix it

The developer who sends the request can fix it; no administrator action is normally needed.

When to contact support

If the error persists after the steps above, contact support@relationsai.com. 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
{
  "error": {
    "code": "idempotency_key_in_progress",
    "message": "A request with this Idempotency-Key is still being processed.",
    "details": {},
    "request_id": "req_5mukun4qwubk7rw5rsxshcr5",
    "retry": "after",
    "doc_url": "https://docs.relationsai.com/errors/idempotency_key_in_progress"
  }
}

Operations that can return this error

• POST /calls: Place a call
• POST /campaigns: Create a campaign
• POST /campaigns/{campaign_id}/recipients: Add recipients
• POST /campaigns/{campaign_id}/start: Start a campaign
• POST /campaigns/{campaign_id}/pause: Pause a campaign
• POST /campaigns/{campaign_id}/resume: Resume a campaign
• POST /campaigns/{campaign_id}/stop: Stop a campaign
• POST /contacts: Create a contact
• POST /contacts/upsert: Create or update a contact by phone number
• DELETE /contacts/{contact_id}: Delete a contact
• POST /dnc-entries: Add a number to the do-not-call list
• DELETE /dnc-entries/{dnc_entry_id}: Remove a number from the do-not-call list
• POST /webhook-endpoints: Create a webhook endpoint
• DELETE /webhook-endpoints/{webhook_endpoint_id}: Delete a webhook endpoint
• POST /webhook-endpoints/{webhook_endpoint_id}/rotate-secret: Rotate a webhook signing secret
• POST /webhook-endpoints/{webhook_endpoint_id}/test: Send a test event
• POST /webhook-deliveries/{webhook_delivery_id}/retry: Retry a delivery

See all codes in the error-code reference.