Could someone clarify why the WFM schedule publish endpoint is suddenly failing with a 500 Internal Server Error when executing our standard weekly publish sequence? This issue emerged last Tuesday during the America/Chicago weekly cycle, specifically when the system attempts to finalize the shift assignments for our inbound support team. The error occurs consistently on the POST /api/v2/wfm/schedules/{scheduleId}/publish call, despite the request payload passing all initial validation checks. We have verified that the schedule configuration remains unchanged from the previous successful publish, and all agent availability constraints are properly defined. The response body provides limited diagnostic information, merely indicating a generic server-side failure without pointing to a specific resource conflict or data integrity issue.
Our environment utilizes a BYOC Edge deployment, and we have confirmed that network connectivity to the Genesys Cloud core services remains stable during the publish window. The error persists even when attempting to publish a minimal test schedule containing only a single agent and a basic shift template, suggesting the issue is not related to payload size or complex constraint calculations. We have also checked the WFM logs for any underlying database lock timeouts or resource exhaustion warnings, but nothing unusual appears in the standard monitoring dashboards. The problem seems isolated to the publish transaction itself, as earlier stages like schedule creation and validation complete without incident.
We are currently unable to finalize the weekly schedule for our Chicago-based workforce, which is impacting our adherence reporting and agent shift swap approvals for the upcoming week. Restarting the integration flow in Architect has not resolved the issue, and clearing the local cache on the BYOC Edge node yielded no improvement. Has anyone encountered a similar 500 error during the WFM publish phase recently? We are looking for potential workarounds or known issues related to the latest Genesys Cloud platform updates that might be affecting the schedule finalization process. Any insights into debugging this server-side error would be greatly appreciated.