I’m completely stumped as to why the schedule publishing process fails with a 403 Forbidden error specifically when targeting our Bring Your Own Cloud (BYOC) Edge deployment. Our standard Genesys Cloud deployment publishes schedules without issue, but the BYOC instance is rejecting the request.
We are using the WFM Scheduling API v2 to automate the weekly schedule publication for our Chicago-based team. The sequence involves calculating schedules via the optimization engine, which completes successfully, followed by a POST to /api/v2/wfm/scheduling/schedules/{scheduleId}/publish. The response body returns:
{
"message": "Access denied. The requested resource is not available in this deployment type.",
"code": "forbidden"
}
The user account performing the publish has the ‘WFM Administrator’ role and explicit permissions for ‘Schedule: Write’ and ‘Schedule: Publish’. These permissions are identical to the account used for our primary cloud deployment. I have verified the access token via the /api/v2/users/me endpoint, and the scopes include wfm:scheduling:write and wfm:scheduling:read.
Is there a known limitation or additional configuration required for WFM scheduling operations on BYOC Edges? The documentation mentions parity between cloud and BYOC for core features, but WFM behavior seems inconsistent. We are running Genesys Cloud version 23.12.0 on the BYOC edge.
I have checked the deployment settings and confirmed that the WFM module is enabled. The issue persists across multiple attempts and different schedule IDs. If this is a known limitation, are there any workarounds to automate schedule publishing for BYOC deployments, or must we rely on manual publishing within the UI?