Summary
A correction is being made to the Agent Schedule Query API to address scenarios where the API previously returned more data than requested.
When requesting agent schedules for one or more work teams, the following cases previously resulted in incorrect behavior:
• If user IDs were provided that are not members of the requested teams, or
• If a schedule was requested for an empty team,
the API would incorrectly return the entire schedule for the management unit instead of restricting results to the requested team(s).
After this change, these requests will return a 400 Bad Request error.
• For unauthorized or unmatched user IDs: wfm.no.authorized.users.in.requested.teams
• For empty teams: wfm.team.empty.or.no.members.in.management.unit
This validation has also been extended to certain historical adherence endpoints to prevent similar issues.
Effective Date
Thursday, December 18, 2025
Customer Impact
Instead of returning full schedules for the management unit—which could include data the requester did not intend to access—the API will now return a validation error, ensuring correct and expected behavior.
Impacted Resources
New possible error codes:
• wfm.no.authorized.users.in.requested.teams
• wfm.team.empty.or.no.members.in.management.unit
Agent Schedule Query
/workforcemanagement/businessunits/{businessUnitId}/weeks/{weekId}/schedules/{scheduleId}/agentschedules/query
Historical Adherence Endpoints (now validating empty teams):
/api/v2/workforcemanagement/managementunits/{managementUnitId}/historicaladherencequery
/workforcemanagement/teams/{teamId}/adherence/historical
Issue References
[WFM-31089]
Contacts
@Brian Trezise
Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.