How do I configure the IVR flow to properly map the API payload without breaking the queue assignment? The new routing integration keeps dropping calls into the general pool instead of the specialized skill groups. It happens every Thursday around 14:00 PT when the external workforce tool pushes the shift changes. The Architect flow shows a 422 Unprocessable Entity error on the /api/v2/architect/flows endpoint during the data lookup step. The response body mentions invalid mapping schema version 2.1. Agent utilization drops to sixty percent because the system routes everyone to the overflow queue. The monitor board just shows static waiting times while actual call volume stays flat. IT says the payload structure changed last week but didn’t update the flow conditions. The team tried restarting the flow version and clearing the cache. The error log still points to the same JSON validation failure. Mic stays hot on the test line but nothing routes correctly. The queue assignment getting confused when the timestamp field arrives in ISO format instead of the expected Unix epoch. Attempts to sync the roster fail immediately. The system not accepting the new schema format. Genesys Cloud version 2024-08 runs the environment. The IVR menu plays the default greeting but the dynamic routing block never triggers. Doing jack all with the current mapping rules. The coaching dashboard reports zero handled interactions for the specialized groups during the sync window. Queue metrics stay frozen until manual intervention. Flow version 4.2 deployment just failed again.