Why does the workforce-management.schedule-assignment.updated webhook payload results in a null employee_id field when routed through the Genesys Cloud Data Action to ServiceNow? The integration was functioning correctly until the recent platform update. The webhook trigger is configured with the standard wfm:read scope, and the Data Action uses the POST method against the ServiceNow incident table API. The raw payload captured in the Genesys Cloud event log shows the employee_id correctly, yet the transformed JSON sent to ServiceNow contains null for this specific field, causing the screen pop logic to fail. The mapping in the Data Action is straightforward, using the body.employee_id path. I have verified the ServiceNow table permissions and the OAuth token validity. The issue persists across multiple test cases with different employee profiles. The error returned from ServiceNow is a 400 Bad Request due to the mandatory field being empty, not a 401 or 403. The timestamp in the payload is also offset by two hours, suggesting a timezone handling issue in the transformation layer, although the source system is set to Europe/London. The documentation for the WFM webhook schema does not mention any recent deprecations for the employee_id field. Is there a known issue with the Data Action transformation engine handling WFM-specific nested objects? I have cross-referenced the API v2 documentation, and the schema remains unchanged. The problem seems isolated to the WFM module, as other webhooks like conversation.started process correctly with the same Data Action structure. Any insights into potential changes in the payload structure or transformation rules would be appreciated. The current workaround involves a manual API call from ServiceNow to fetch the employee details, but this adds significant latency to the ticket creation process. The goal is to restore the real-time automation without introducing additional API calls. The environment is Genesys Cloud EU, and the ServiceNow instance is London-based. The Data Action version is the latest stable release. I have checked the integration logs, and no syntax errors are reported during the transformation step. The issue appears to be a silent failure in the field mapping. Has anyone encountered similar nullification issues with WFM webhooks in the last month? I am looking for a definitive solution to avoid relying on manual workarounds. The impact on our service desk is significant, as the automated ticket creation is a critical part of our workflow. Any assistance in identifying the root cause would be greatly valued. I am prepared to provide sample payloads and transformation configurations if needed for further debugging. The urgency is high, as the manual process is not sustainable for our volume. I have escalated this to Genesys Support, but they have suggested checking the community for similar issues. I am hopeful that someone with experience in WFM integrations can provide a quick fix. Thank you in advance for any guidance.