So I’m seeing a very odd bug with the Predictive Routing API when attempting to assign skill groups to agents via the /api/v2/routing/skills endpoint. The ServiceNow integration script is sending a valid JSON payload but receives a 400 Bad Request error indicating an invalid skillId format.
The environment is Genesys Cloud Engage (London region) and the script utilizes standard OAuth2 client credentials. I have verified the skillId exists and is active within the routing configuration, yet the API rejects the assignment consistently.
Has anyone encountered this specific validation error during automated skill provisioning? Looking for insights on potential payload formatting issues or known API quirks.