WFM API 409 Conflict on Bulk Schedule Publish via ServiceNow

Anyone free to help troubleshoot this 409 Conflict error when pushing schedule data from ServiceNow to Genesys Cloud WFM.

The issue occurs specifically during bulk publish operations using the /api/v2/wfm/scheduling/schedules endpoint. Individual agent updates succeed, but batches exceeding 50 records fail with a timestamp collision error.

Has anyone implemented a retry logic or batch chunking strategy within ServiceNow scheduled jobs to handle this WFM rate limiting?

• Reduce batch size to 20 records per request
• Add a 500ms delay between batches to avoid the 409 conflict

The quickest way to solve this is… to verify the timezone alignment between ServiceNow and the WFM schedule. A 409 often indicates a metadata mismatch rather than rate limiting. Ensure the scheduleId is unique per batch and check for overlapping intervals. Use exponential backoff if collisions persist.