Does anyone understand why the Genesys Cloud Predictive Routing Data Action webhook is consistently timing out with a 504 Gateway Timeout when attempting to sync deep skill hierarchies to ServiceNow (Tokyo Release) via the cmdb_ci_service REST API? The environment is Genesys Cloud UK East, operating on the latest release, with ServiceNow configured for automated incident creation and screen pop triggers. The Architect flow is designed to capture routing profile updates and push them to ServiceNow to maintain CMDB accuracy. The issue arises specifically when the skill hierarchy exceeds three levels of depth. The webhook payload, constructed using the Data Actions module, includes nested JSON objects for each skill level. When the payload size exceeds approximately 15KB, the Genesys Cloud connector fails to establish a stable connection with the ServiceNow instance, resulting in the 504 error. The ServiceNow logs indicate that the request is received but times out during the glideAjax processing phase, suggesting the bottleneck is within the ServiceNow script include handling the complex JSON parsing. The Content-Type is set to application/json, and the Authorization header uses a valid OAuth2 token with appropriate scopes. The Retry policy in the Data Action is set to 3 attempts with a 5-second delay, but all retries fail. The Debug logs in Genesys Cloud show the outbound request is successful, but the response from ServiceNow is never returned within the 30-second timeout window. The integration works flawlessly for shallow skill structures, indicating the issue is related to payload complexity rather than connectivity or authentication. The ServiceNow side is running the Update Set for the custom integration module, which handles the JSON deserialization. The API endpoint is https://<instance>.service-now.com/api/now/table/cmdb_ci_service. The Payload includes name, description, and nested skills arrays. The Error message in the Data Action log is Timeout waiting for response from target URL. The Environment variables are correctly set, and the Firewall rules allow outbound traffic on 443. The Load Balancer in front of ServiceNow is not rejecting the request, as confirmed by the ServiceNow gateway logs. The Integration is critical for maintaining accurate routing metrics in the ServiceNow CMDB. The Workaround currently involves manually syncing skills, which is unsustainable. The Documentation for Data Actions mentions a 1MB payload limit, which is not being approached. The Issue persists across multiple Architect flows and Data Actions. The Goal is to identify if there is a known limitation with JSON parsing in ServiceNow Tokyo or if the Genesys Cloud connector is prematurely terminating the connection. The Request is for any insights on optimizing the Payload structure or adjusting the Timeout settings in the Data Action configuration. The Context includes the Skill hierarchy depth, Payload size, and ServiceNow processing time. The Expectation is a solution that allows for deep skill hierarchy syncing without Timeout errors. The Urgency is high, as the CMDB data is becoming stale. The Impact includes inaccurate Predictive Routing metrics and ServiceNow ticketing delays. The Next Steps involve reviewing the ServiceNow script include for optimization and potentially breaking down the Payload into smaller chunks. The Question is whether there is a best practice for handling large JSON payloads in Genesys Cloud Data Actions when integrating with ServiceNow.