why does this setting in the agent scripting module throw a 400 bad request error when i try to update script associations via the /api/v2/wfm/schedules/agentscripts endpoint? we are running into this consistently during our weekly publication window on tuesdays at 08:00 cst. the flow hangs and then fails with a constraint violation message about invalid script id format.
here is the exact payload we are sending:
{
“agentId”: “5f9a8b7c-1234-5678-9abc-def012345678”,
“scriptId”: “script-inbound-sales-2024”,
“effectiveDate”: “2024-05-15T08:00:00.000Z”
}
the script id exists and is active in the system. i have verified this through the ui. however, the api insists it is malformed. this is really frustrating because we have an automated workflow in architect that relies on this update to ensure agents have the correct scripts loaded before their shifts start. the workflow uses the wfm schedule data action to pull agent lists and then loops through them to assign scripts.
i noticed that if i change the script id to a numeric value it works, but our scripts are named with dashes for clarity. is there a hidden constraint on the api that requires numeric ids only? the documentation does not mention this. also, the error message is not very helpful. it just says “invalid script id format” without specifying what format is expected.
we are using the latest version of the rest api v2. our environment is us-east-1. this issue has been ongoing for two weeks now and is causing delays in our schedule publication process. agents are starting shifts without the correct scripts assigned, which leads to compliance issues.
has anyone else encountered this specific error with the agent scripting api? any workarounds or suggestions would be greatly appreciated. i am considering switching to the bulk update endpoint but that seems even less documented. thanks in advance for any help.