Trying to make sense of why the Data Action node in our primary IVR flow is consistently returning a 504 Gateway Timeout when attempting to create an incident record in ServiceNow via the POST /api/v2/dataactions/execute endpoint. The flow handles high-volume inbound calls during UK business hours (Europe/London), and while the payload validation passes locally, the execution fails specifically when the incident.priority field is set to 1 - Critical. We are using the latest Genesys Cloud Architect version and have verified that the ServiceNow instance is reachable from the Genesys Cloud VPC endpoint. The error log indicates a connection reset after 30 seconds, which suggests a potential issue with the webhook payload size or the ServiceNow API rate limiting, but we have already increased the timeout settings in the Data Action configuration. Can someone clarify if there are specific payload constraints or header requirements for critical incident creation that might be causing this latency? The integration worked perfectly until the last release, and we have not changed the ServiceNow script includes or the Genesys Cloud flow logic. Any insights into the expected behavior or known issues with this specific endpoint would be appreciated.