What is the standard approach to handle WFM schedule publish failures when digital messaging agents are assigned to specific skill groups during the weekly publish window in the America/Chicago timezone? Our team manages a BYOC Edge deployment and we are encountering a persistent 500 Internal Server Error when executing the standard weekly publish sequence for our digital messaging queue. This issue emerged last Tuesday during our routine schedule publication, specifically when the WFM module attempts to reconcile agent availability with the digital messaging skill group assignments. The error occurs at the final stage of the publish process, after all shift swaps and time-off requests have been validated, but before the final schedule is committed to the production environment. We have verified that all agent profiles are correctly configured with the necessary digital messaging skills, and the shift swap validation endpoint is returning 200 OK for all pending trades. However, the publish job fails with a generic 500 error, and the detailed logs only show a timeout exception when the WFM service attempts to update the digital messaging agent status in the Genesys Cloud CX platform. This is causing significant delays in our weekly scheduling process, as we are forced to manually intervene and republish the schedule in smaller batches to avoid the timeout. We are using the latest version of the WFM scheduling API, and our BYOC Edge instance is up to date with the most recent patches. The issue seems to be isolated to the digital messaging skill groups, as our voice and chat queues publish without any problems during the same window. Could someone explain why the WFM schedule publish endpoint is failing specifically when digital messaging agents are involved, and what steps we can take to resolve this timeout issue? We need a reliable solution to ensure our weekly publish process runs smoothly without manual intervention.