Quick question about the v2 agent preferences endpoint. We are hitting a 422 Unprocessable Entity error when pushing shift swap constraints via the bulk API. The payload validates locally, but the server rejects the timezone offset format for our Chicago agents.
Is there a specific ISO 8601 variant expected for the start_time field? The documentation is vague on this, and our integration script is failing consistently for agents in the America/Chicago zone.
Pretty sure the v2 endpoint expects UTC offsets without colons.
2023-10-27T08:00:00-0500.It depends, but generally… the issue likely stems from how the bulk payload handles nested objects versus flat arrays. While the colon-less offset mentioned in the suggestion above is valid for single-record updates, the bulk endpoint often expects a strictly ISO 8601 format with the colon intact (-05:00) to avoid parsing ambiguity during batch validation. The 422 error frequently triggers when the server attempts to normalize timezone data across multiple agents simultaneously.
Try restructuring your JSON payload to ensure the start_time fields are explicitly tagged as strings rather than relying on implicit conversion. Also, verify that the agent preferences schema version in your request header matches the current API spec. Bulk operations are notoriously sensitive to schema drift, and a minor mismatch can cause the entire batch to fail. If the problem persists, isolate a single agent record to confirm it is indeed a timezone formatting issue rather than a constraint logic conflict within the WFM engine.