Internal rate limiter blocking calls triggering under high concurrency
Created
Feb 27 at 09:23am EST
We identified an issue preventing calls from being triggered when a large volume was submitted within a short period of time. In such cases, an internal rate-limiting mechanism was activated, blocking the calls from being triggered.
As a workaround, we provide a dedicated batch webhook endpoint that allows a large number of calls to be triggered at once. Clients should use this endpoint instead of the individual call-triggering endpoint to avoid encountering rate limits.
To address this more robustly, we are developing a new gateway infrastructure specifically designed for call triggering. This gateway will support higher rate limits and handle forwarding calls to downstream systems in a controlled manner, allowing clients to submit high volumes of calls while preserving downstream rate constraints.
This development is currently in progress. In the meantime, clients are advised to use the dedicated batch webhook endpoint.
Affected services