Looking for advice on handling rate limiting for outbound digital messaging webhooks. Our AppFoundry integration is experiencing intermittent 429 Too Many Requests errors when Genesys Cloud pushes conversation events to our endpoint. The issue spikes during PST morning rush hours (8-10 AM). The response headers indicate we are hitting the standard API rate limit, but these are inbound webhooks from Genesys, not outbound calls from our server. We are using the latest Architect flow configuration with a 30-second timeout. The payload size is minimal, under 1KB. We have verified that our server can handle the throughput using load testing tools. The error log shows: “HTTP 429: Rate limit exceeded. Retry after 60 seconds.” This causes a backlog in our message queue and delayed responses for end users. Has anyone configured a custom rate limit or a different webhook strategy for high-volume digital channels? We are considering implementing exponential backoff on our server, but that introduces latency. Is there a way to increase the webhook throughput limit via the API or account settings? Thank you for your insights.