Is it possible to configure a Data Action in Genesys Cloud that reliably creates ServiceNow incidents when triggered by Predictive Routing wrap-up codes, without hitting rate limits? We are seeing intermittent 429 errors during peak London morning hours.
The flow uses an HTTP POST to the ServiceNow REST API. Payloads are small, but volume spikes cause Genesys to drop requests before they reach the target. Logs show successful intent matching but failed external calls.
Has anyone tuned the retry logic or batch size for this specific integration pattern? We need a stable bridge between wrap-up data and ITSM ticketing.