25109: Request is rate limited
ERROR
Twilio rejected the request because your application exceeded the allowed request rate for this operation. This error helps protect the Verify service from bursts of traffic that can affect performance or indicate an unexpected retry pattern.
- Your application sent too many Verify API requests in a short period of time.
- Your integration retried requests too aggressively after a timeout or non-success response.
- Multiple application instances or workers sent requests concurrently without rate limiting.
- A bug or traffic spike caused an unexpected increase in verification requests.
- You exceeded a service limit associated with your Verify use case.
- Reduce the rate of requests from your application and retry with backoff instead of sending requests continuously.
- Review your retry logic and make sure you do not immediately resend failed requests in a tight loop.
- Add client-side rate limiting, request queuing, or throttling across all workers and services that call Verify.
- Confirm that the traffic pattern is expected and that your application is not generating duplicate verification requests.
- If the traffic is valid for your use case, review your Verify implementation and contact Support to discuss your request pattern and applicable limits.