Running into a hard stop with an HTTP POST Data Action in Architect. The external service is slow, taking about 4.5s to respond, but Genesys Cloud cuts the connection after exactly 3000ms. I’ve checked the docs and the UI, but there’s no obvious field to bump this timeout. The error payload is generic: "error": "Request timeout". I’ve tried adding headers like X-Genesys-Timeout but that gets stripped or ignored. Is there a hidden parameter in the JSON config or an API flag I’m missing? Here’s the relevant part of the Data Action definition I’m using via the API:
{
"name": "PostToLegacySystem",
"type": "http",
"config": {
"method": "POST",
"url": "https://api.legacy-system.com/process",
"headers": {
"Content-Type": "application/json"
},
"body": "{{input.payload}}",
"timeout": 3000
}
}
I’ve manually edited the timeout field to 5000 in the JSON editor before saving, but Architect resets it back to 3000 on save. It seems hardcoded. I’ve looked through the genesyscloud-dataaction Terraform resource attributes and there’s no timeout argument listed. This is blocking a critical integration. Can I override this via the REST API directly, maybe with a different endpoint version? Or is this a platform-wide hard limit for HTTP data actions? I’ve also tried using a webhook pattern with a polling mechanism, but that adds unnecessary latency and complexity. Just want to know if there’s a way to extend this window without waiting for a feature request to be prioritized. The service is reliable, just slow. Any workarounds or API tricks?