Anyone know why the workforce management schedule:published webhook payload appears to be truncating agent availability data when ingested by our ServiceNow MID server? We are running Genesys Cloud 2024.06.0 and ServiceNow Washington DC. The integration uses a Data Action to parse the JSON and create records in the wfm_schedule table. However, the MID server logs show a 400 Bad Request with error message ‘Invalid JSON: Unexpected end of input’. This occurs specifically during peak shift changes between 08:00 and 09:00 GMT. The webhook endpoint is https://mid-server.service-now.com/api/global/wfm_integration. We have verified the payload structure using the Genesys Cloud API Explorer, which returns complete data with all agent_id and shift_start fields. The issue seems isolated to the webhook delivery mechanism rather than the ServiceNow REST message configuration. We have increased the MID server timeout to 30 seconds, but the truncation persists. The Data Action logs show the input variable truncating after 1500 characters. Is there a known limitation on webhook payload size for WFM events, or should we be implementing pagination for these specific triggers? We need a reliable method to sync full schedule data without hitting the 400 errors on the MID server.