My configuration keeps failing… The POST /api/v2/wfm/schedule/publications endpoint is rejecting our weekly schedule push with a 400 Bad Request. The error payload specifically flags an issue with the agent_scripts association in the schedule payload.
We are using the Genesys Cloud WFM SDK v3.12.0. The schedule publishes fine when agent scripts are omitted, but compliance requires the “Chicago_Compliance_Prompt_v2” script to be attached to all inbound shifts for the America/Chicago timezone.
The YAML structure for the schedule item looks correct based on the Swagger definition, yet the validation service throws a VALIDATION_ERROR: Invalid script assignment for shift type.
yaml
scheduleItems:
- agentId: "a1b2c3d4-..."
weekStartDate: "2023-10-23T00:00:00.000Z"
shifts:
- startTime: "2023-10-23T08:00:00.000Z"
endTime: "2023-10-23T16:00:00.000Z"
state: "IN"
scriptId: "script-id-chicago-compliance-v2"
scriptName: "Chicago_Compliance_Prompt_v2"
skillAssignments:
- skillId: "skill-inbound-sales"
skillName: "Inbound Sales"
Is there a known limitation with attaching scripts during the initial publication phase versus updating them post-publication? Our team is blocked on finalizing the October schedules.