We’re pushing Queue Settings updates through the Platform API because the Admin UI keeps timing out on bulk changes. The routing queue payload keeps rejecting the WRAP_UP_TIME and SKILLS arrays with a 400 validation error. Console shows the org is on the standard US-East cluster, and the Python SDK version’s locked to 12.0.4. Tried stripping the payload down to just the queue_id and acd_settings, but the response still flags the skills object as malformed. The Admin UI handles this exact configuration without hiccups, so the API schema must be stricter on the nested Routing Rules. Architect Flow isn’t even triggered yet, just the initial settings sync. Console Logs aren’t showing anything useful, just the raw 400 dump. Replaced the skill IDs with UUIDs from the directory, still get the same rejection.
PUT /api/v2/routing/queues/8f3a2b1c-4d5e-6f7a-8b9c-0d1e2f3a4b5c/settings
{
"error": "invalid_request",
"message": "Validation failed: skills[0].id must be a valid skill identifier",
"status": 400,
"code": "bad_request"
}