What is the correct way to handle script updates during shift swaps

Is there a clean way to handle dynamic script updates when agents execute shift swaps in the WFM module? We are seeing inconsistencies in the Architect flow where the script version does not match the agent’s new shift parameters.

Our environment runs Genesys Cloud v24.5.0 in the Chicago region. The issue surfaces specifically when an agent swaps shifts close to the 17:00 CST publish window. The wfm:schedule:publish event triggers, but the associated script assignment in Architect seems to retain the previous shift’s metadata.

We are using the standard API to fetch script content based on the agent’s current schedule slot. However, after a swap, the getScript endpoint returns the old version until the agent logs out and back in. This breaks our compliance recording logic which relies on the correct script variant for the new time block.

Is there a specific webhook or real-time update mechanism we should be leveraging to sync script assignments immediately upon a successful shift swap? We need to ensure the Architect context refreshes without requiring a full session reset.