Just noticed that HTTP 400 Bad Request hits whenever our WFM scheduler tries to trigger a script update via the Agent Scripting API during active shift swap windows.
Environment: Genesys Cloud US1, API v2. The payload validates fine in Postman but fails in production when tied to schedule adherence checks. Is there a known lock on script resources during real-time schedule modifications? Looking for workarounds to prevent this cascade failure in our weekly publish jobs.