I’m completely stumped as to why the Genesys Cloud API returns a 400 Bad Request when pushing skill weights for predictive routing during our Zendesk tag migration. The request to update user routing skills rejects the payload despite valid JSON structure matching the Zendesk tag hierarchy. Our EU1 environment uses the latest Admin SDK. Is there a specific constraint on skill weight values when migrating from Zendesk’s flat tag system to Genesys’ hierarchical skill set? Why does the validation fail on numeric precision?
1 Like