​

Retry Logic

​

Configuration

{
  "phone": "+14155551234",
  "name": "John Doe",
  "agentId": "agent_abc123",
  "retryConfig": {
    "retryCount": 3,
    "retryDelays": [5, 15, 30]
  }
}

​

Parameters

​

How Retries Work

1. The initial call is placed immediately
2. If the call fails (busy, no answer, error), the system waits for the first delay
3. Before each retry, credits are re-checked if insufficient, the retry is skipped
4. The process repeats until either:
   • A call connects successfully
   • All retry attempts are exhausted
   • The call is cancelled via API

Initial call ──▶ FAIL ──▶ wait 5min ──▶ Retry 1 ──▶ FAIL ──▶ wait 15min ──▶ Retry 2 ──▶ SUCCESS

​

Retry Delays Example

​

Credit Pre-Check on Retry

• If credits are available → retry proceeds
• If credits are insufficient → retry is skipped, contact marked as failed

​

Cancelling Retries

curl -X DELETE https://client-backend.oktivo.com/api/v1/crm/calls/{contactUID} \
  -H "Authorization: Bearer okt_your_token_here"

​

Monitoring Retries

curl https://client-backend.oktivo.com/api/v1/crm/calls/{contactUID} \
  -H "Authorization: Bearer okt_your_token_here"

• attempts how many attempts have been made so far
• retryConfig the original retry configuration
• status current contact status (pending, in_progress, completed, failed, stopped)
• lastError reason for the most recent failure

​

Best Practices

• Start with short delays (5 min) for first retry, increase for subsequent attempts
• Use 2–3 retries for most use cases more than 3 rarely improves connection rates
• Monitor credit consumption each retry attempt consumes credits independently
• Set up webhooks for call.failed to track contacts that exhaust all retries
• Consider time of day longer delays may push retries into off-hours