Rate limits

Okatana rate limits external calls per credential. A limit response uses HTTP 429.

The SDK maps this to OkatanaRateLimitException. If the server provides Retry-After, the exception exposes it as RetryAfter.

try
{
    await client.Organizations.GetAsync(organizationId, cancellationToken: cancellationToken);
}
catch (OkatanaRateLimitException ex)
{
    logger.LogWarning("Okatana throttled this workload. Retry after {Delay}", ex.RetryAfter);
    throw;
}

Safe GET retries can wait and retry a 429 automatically. Write requests do not automatically retry unless explicitly configured.

For sustained workloads, use pagination sizes near the API maximum when appropriate, cache read-only lookup data for a bounded period, avoid polling faster than business needs, and use separate least-privilege credentials for unrelated workloads instead of making one broad token a system-wide bottleneck.