Does anyone know… the exact threshold or mitigation strategy for 429 Too Many Requests errors when pushing real-time messaging transcript updates from Genesys Cloud to ServiceNow via custom Data Action webhooks? We are experiencing intermittent failures in our EU-West-1 BYOC environment where the Architect flow triggers a webhook immediately upon message receipt. The ServiceNow instance is configured with standard REST message limits, yet the GC outbound requests are being throttled despite valid OAuth 2.0 tokens and correct Content-Type headers. The error payload indicates X-RateLimit-Remaining: 0, suggesting the GC side or the intermediate VPC endpoint is hitting a ceiling before reaching SNOW. We have verified the payload size is under 1KB and the frequency is roughly 150 messages per minute during peak hours. Is there a specific header or configuration in the GC webhook settings to implement exponential backoff, or must this be handled entirely within the ServiceNow script include? The documentation mentions rate limits but lacks specifics for high-volume digital channel integrations.