Outbound Campaign API 409 Conflict during Weekly Schedule Sync

General Discussion
1

Can anyone explain why the POST /api/v2/outbound/campaigns endpoint is returning a 409 Conflict when I attempt to update campaign capacity settings immediately after publishing the weekly WFM schedule?

Our Chicago team uses a tight integration between WFM and Outbound. We publish schedules every Sunday night. The goal is to adjust the campaign’s max concurrent calls based on the new headcount available in the next week’s roster.

Steps to reproduce:

  1. Publish the weekly schedule via WFM API (status: 200 OK).
  2. Wait 10 seconds to allow for cache propagation.
  3. Call PUT /api/v2/outbound/campaigns/{campaignId} to update the ‘capacity’ field.
  4. Receive a 409 Conflict response with the message: “Campaign configuration is locked due to ongoing schedule reconciliation.”

This is frustrating because the documentation suggests the lock should release within 5 seconds. We are using the Genesys Cloud SDK v2.5.1. The error persists even if I increase the delay to 60 seconds. Is there a specific webhook or event I should be listening to instead of a hardcoded wait time? The schedule adherence data looks correct in the UI, so the conflict seems to be an internal state issue rather than a data validation error.