The schedule publishing process is doing jack all this morning. Console shows everything green, but the automated shift trade approval flow keeps bombing out. It’s supposed to check agent preferences and time-off overlaps before pushing the updated roster via the /api/v2/wfm/schedules/publish endpoint. Platform version is 2024-07.0, US East environment.
The REST API action returns a 422 Unprocessable Entity with this payload:
{
"code": "badRequest",
"message": "Schedule adherence constraints violated for agent IDs: 7842, 9911",
"details": "Field 'preferred_shift_type' expects enum value but received null"
}
Logs show the flow is passing the correct agent IDs, but the WFM API seems to be stripping out the shift preference data after the first merge step. Checked the schema in the developer portal, don’t see any changes. Rebuilt the JSON mapper in Architect, still throws the same error. Mic stays hot while the queue fills up. The adherence rules are locked to standard business hours, yet the API keeps flagging null values for agents who explicitly set their preferences in the self-service portal.
API response headers show x-genesys-correlation-id: 8f3a2c1d-99b4-4e2a-a1c7-f8b2d4e5c6a7.