I’ve spent hours trying to figure out why the POST /api/v2/routing/skillgroups endpoint returns a 400 Bad Request when attempting to replicate Zendesk Support Groups as Genesys Cloud Skill Groups. The error response indicates that the routing_skill reference is invalid, yet the UUID corresponds to an active skill in our tenant. We are migrating our Zendesk routing logic, where tags define agent capabilities, into Genesys Cloud Roster Groups and Skill Groups. In Zendesk, we rely on dynamic tag-based automation, but Genesys Cloud requires static skill assignments for predictive routing to function. The payload includes a valid routing_skill.id and name, but the API rejects it with "message":"The requested resource was not found". I have verified the skill exists via GET /api/v2/routing/skills/{skillId}. Is there a specific permission or configuration step required in the Genesys Cloud admin portal to enable skill group creation for migrated entities? The documentation suggests a direct mapping, but the API behavior implies a dependency on an underlying routing configuration that we might have missed during the initial tenant setup.