RVR-GNS-429

Issue Summary

The error code RVR-GNS-429 with the description TOO_MANY_REQUESTS indicates that you have hit the rate limit imposed by the Genesys data connector within Rivery. This usually happens when the number of requests sent to the Genesys API exceeds the allowable rate limit within a specified window of time. Rate limiting is implemented to maintain the stability and performance of the service.

Action Steps

1. Understand the Rate Limiting:

   • Check the Genesys API documentation to understand the specific rate limits associated with the API endpoints you are using. Knowing the exact limits (e.g., requests per second, requests per minute) will help you adjust your request rate accordingly.

2. Optimize Request Rate:

   • Reduce the frequency of requests made to the API. You can achieve this by implementing a delay or sleep between requests to ensure that you stay within rate limits.
   • Consider batching multiple requests into a single request if the API allows for this functionality. This reduces the number of individual requests made.

3. Implement Exponential Backoff:

   • If you encounter a 429 TOO_MANY_REQUESTS response, implement an exponential backoff strategy, where subsequent requests are delayed progressively longer after each failure. This strategy helps manage retries effectively without immediately hitting the rate limit again.

4. Review Rivery Settings:

   • Within Rivery, adjust the scheduling of your rivers to run at times when the API is under less load or configured to run less frequently if you are consistently hitting the limit.

5. Contact Genesys Support:

   • If reducing the request rate is not possible due to operational needs, contact Genesys support to discuss potential adjustment of rate limits for your application.

External References

• You can review specific Genesys API rate limiting details in the Genesys Developer Portal: Genesys API Rate Limiting.

If the issue persists or you need further assistance, please open a ticket with Rivery support.