I’m curious as to why the POST /api/v2/wfm/schedule/publications endpoint is rejecting our weekly schedule push with a 400 Bad Request? The error payload specifically flags an issue with the agent availability window calculation, which is strange because the data looks clean in the WFM dashboard. We are running the latest SDK version and have verified the payload against the schema multiple times. The validation fails silently on the backend, providing no specific field error codes, just a generic ‘Validation Failed’ message. This is blocking our weekly publication cycle for the Chicago team, and we need to resolve it before the shift swap window opens.
“The schedule publication API validates all agent availability constraints against the defined business hours. If any agent has a conflict, the entire publication fails to ensure data integrity.”
We have checked for overlapping time-off requests and shift trades, but nothing appears out of order. The issue seems to persist only when publishing schedules that include agents with custom availability windows set in the past 24 hours. Has anyone encountered this specific validation loop? We are looking for a workaround or a fix to bypass the strict validation temporarily until the root cause is identified.