Getting 408 Request Timeout on every external API call from our Architect flow. The script handling the webhook response is solid and returns JSON in roughly 1.2s when tested locally with curl. But in production, inside the Genesys Cloud flow, it consistently fails.
Here is the configuration for the Data Action:
{
"method": "POST",
"url": "https://api.internal.wfm-tool.com/v2/update-status",
"headers": {
"Content-Type": "application/json",
"Authorization": "Bearer {{token}}"
},
"body": "{\"userId\": \"{{user.id}}\", \"status\": \"adherent\"}"
}
The error log in the flow execution trace shows:
Data action failed: Timeout waiting for response from external service. Max wait time: 3000ms.
I’ve checked the documentation, and it mentions a default timeout of 3000ms. We need it to be at least 5000ms because some of these calls hit the database during peak hours in our Pacific timezone shifts. There’s no obvious field in the Data Action JSON schema for timeout or requestTimeout. I tried adding "timeout": 5000 to the root object, but Architect rejects the schema validation with a 400 Bad Request saying the field is not allowed.
Is there a global setting in the API or a specific header I can inject to override this 3s hard limit? Or is this a platform constraint we can’t touch? We’re building a real-time adherence tracker, and losing these updates breaks our queue logic. The WFM team is complaining about stale data. I need a code-level fix, not a architectural redesign.