We are running a hybrid integration where an Architect flow triggers a custom Data Action to push call disposition data to our internal Node.js service. The service endpoint is healthy and responds in roughly 400ms under normal load. However, during peak hours, the response time spikes to just over 3 seconds, causing the Data Action to fail with a timeout error.
I’ve verified the timeout setting in the Data Action configuration via the Genesys Cloud UI and also checked the definition via the API. The timeout is explicitly set to 3000 milliseconds. I assumed this was a hard limit, but I recall seeing documentation suggesting it might be adjustable or that there’s a different mechanism for longer-running integrations.
Here is the relevant snippet from the Data Action definition JSON:
{
"type": "custom",
"name": "PushDisposition",
"timeout": 3000,
"url": "https://internal-api.example.com/disposition",
"method": "POST",
"headers": {
"Authorization": "Bearer {{token}}",
"Content-Type": "application/json"
},
"body": {
"callId": "{{interaction.id}}",
"disposition": "{{dispositionCode}}"
}
}
The error log in the Architect flow shows:
Data action 'PushDisposition' timed out after 3000ms. Response status: 504 Gateway Timeout
We’ve tried increasing the timeout in the UI to 5000, but it seems to revert or get ignored, still failing at the 3-second mark. Is there a specific API parameter or a different Data Action type we should be using to handle responses that take between 3 and 5 seconds? We don’t want to move this to an async webhook pattern if a simple sync increase is possible.
We are using the us-east-1 region. Any pointers on how to bump this limit?