My configuration keeps failing when executing batch updates for agent shift preferences via the /api/v2/wfm/schedules endpoint. The request returns a 400 Bad Request error, citing invalid time formats for entries scheduled after 18:00 CST. This disrupts our Tuesday publishing workflow significantly.
The payload structure matches the documentation exactly. Any insights on handling timezone conversions for Chicago-based shifts within the JSON body would be appreciated. We need this resolved before the weekly cycle closes.