Hi all, try to run batch check for shift trades during weekly publish edge case. Use /api/v2/workforcemanagement/businessunits/{businessUnitId}/shifttrading/trades/evaluate/jobs but it is coming error. Agent preferences not matching for some users in Tokyo org.
{
"message": "Invalid request",
"code": "bad.request",
"status": 400
}
Try change body payload but still fail. Don’t know why it’s not working for these specific trades.
The 400 error usually means there’s a mismatch in the request body or the business unit ID. If the agent preferences aren’t matching, it’s often because the payload has a field that the system doesn’t recognize for those specific users. Try using the forceAsync=true query parameter in the POST request to /api/v2/workforcemanagement/businessunits/{businessUnitId}/shifttrading/trades/evaluate/jobs to see if it bypasses the immediate validation error.
There was a community post a while back about similar WFM API errors where the body was too large for a batch check. A good workaround is to split the users into smaller groups instead of one big list. Check if the businessUnitId is exactly correct for the Tokyo org since a small typo there will trigger a bad request.