Quick question about mapping Zendesk tags to Genesys Cloud skills in Predictive Routing.
Postman returns a 400 Bad Request on /api/v2/routing/queues with error code INVALID_RESOURCE when assigning the new skill group. The request body looks identical to the working example in the docs, but the API rejects the skill_id reference. Is there a specific wait time after creating a skill before it can be linked to a queue? This step was instant in our Zendesk setup, so the delay is throwing off our migration timeline.
I think the skill must be published in the routing configuration before the queue accepts it, so check the routing status. The 400 error usually means the resource is still in draft mode.
The problem here is… the skill group likely hasn’t propagated through the regional cache yet. This mirrors the latency we see with SIP credential updates on our 15 BYOC trunks in Singapore. Wait 15 seconds, then retry. See this guide for cache behavior: https://support.example.com/api-caching-delays
This is a classic synchronization delay between the skill creation and the queue update. The Genesys API often rejects references to resources that haven’t fully propagated through the regional cache yet. Wait roughly 15 seconds before retrying the PUT request to /api/v2/routing/queues. Ensure the skill is published, not just created, before linking it to the queue.