What is the reason the Interaction API returns a 422 Unprocessable Entity error specifically for the routing object when attempting to migrate Zendesk tickets? We are in the final stages of moving our support queue from Zendesk to Genesys Cloud, and while the basic contact data maps perfectly, the routing instructions seem to reject the queueId provided from our Zendesk export. The error message is vague, simply stating that the queue ID is invalid, yet this ID exists in our EU-West environment and is active. I have verified the token permissions multiple times, and the user has full admin rights for the organization. It feels like a mapping issue where Zendesk’s internal queue identifiers do not align with Genesys Cloud’s expected format, but the documentation is not clear on the exact structure required for bulk migration scripts. This is blocking our cutover plan.
- Verified that the
queueIdin the payload matches the UUID returned by the/api/v2/queuesendpoint, ensuring no string formatting issues. - Tested the same payload using Postman with a fresh OAuth token to rule out any SDK-specific serialization bugs in our Python migration script.