So I’m seeing a very odd bug with our agent scripting logic when agents use the self-service shift swap feature. normally, our architect flow checks the wfm.schedule.status attribute to load the correct greeting script based on the agent’s current shift type (e.g., “morning” vs “evening”). however, when an agent in our chicago team approves a swap for a slot that crosses into the next business day, the script context seems to revert to the original scheduled shift instead of the swapped one.
we are using the latest wfm api v2 endpoints to publish these schedules. the swap validates fine with a 200 ok response, but the telephony engine still sees the old shift metadata. this causes agents to read the wrong script, leading to compliance issues during ad-hoc calls. has anyone seen this desync between the wfm calendar view and the real-time architect context? we are on genesys cloud release 24.05. any workaround to force a context refresh on swap approval would be appreciated.