The adoption metrics dashboard is currently blank for the Q3 compliance training plan, and stakeholder buy-in is evaporating. The POST /api/v2/wem/users endpoint keeps throwing 403 Forbidden when pushing mandatory security groups, so the rollout is stalled. Tried the workaround from that community thread about the WEM sync loop to reset the batch operation type, but the agent profiles are doing jack all and the training dependencies aren’t resolving.
The common gotcha is missing the wem:users:write OAUTH SCOPE.
curl -X POST "https://api.mypurecloud.com/api/v2/wem/users" \
-H "Authorization: Bearer <TOKEN>" \
-H "Content-Type: application/json" \
-d '{"name": "Compliance Group"}'
You’ll need to adjust the SECURITY GROUP mappings inside the ARCHITECT FLOWS before the dependency resolves. Architect flows remain the preferred routing method here. The batch operation type reset won’t bypass scope validation. Direct API pushes always fail without the correct CONFIGURATIONS.