Quick question about Agent Scripting API 409 during publish

  • Quick question about the /api/v2/wfm/scheduling/v2/schedules endpoint returning a 409 Conflict when pushing script configurations alongside shift updates.
  • Using the v2 SDK in Python, the payload includes valid scriptId references, but the scheduler rejects it citing overlapping resource locks despite no active agent swaps.
  • Is there a specific header or sequence required to bypass the lock when scripting changes are involved?