Why does the /api/v2/wfm/schedules/publish endpoint returns a 502 Bad Gateway when Digital Messaging channels are active?
Genesys Cloud Release: 2024.2 (US-East-1)
WFM Module: Version 10.5.1
Environment: BYOC Edge with custom routing rules
The error occurs specifically when publishing schedules for agents assigned to Digital Messaging queues with high concurrency settings. Our Chicago team relies on instant shift swap updates, but this blocks the entire publishing process. Is there a known limitation with concurrent WFM and Digital Messaging API calls?