Stuck on mapping Zendesk ticket contexts into Genesys Cloud Architect flows during our migration sprint. The legacy system passes ticket metadata via a custom header, but the new Genesys Cloud IVR setup using the latest Architect version seems to drop the payload when transitioning from the voice channel to the digital handoff. Specifically, the set-attribute action fails to capture the Zendesk ticket ID correctly, resulting in a null reference error downstream in the script. We are using the standard OAuth 2.0 client credentials for the API calls, and the edge region is set to Europe-West-1 (Frankfurt) to match our primary Zendesk instance. The error log shows a 400 Bad Request when the flow attempts to validate the external data source connection. It feels like the schema mapping for the interaction context is incomplete. Has anyone successfully bridged Zendesk ticket tags to Genesys Cloud user attributes in a similar BYOC environment? We need a reliable way to ensure the agent sees the full ticket history without manual lookup.