Why does the shift swap API rejects valid payloads with a 422 Unprocessable Entity error?
Our Chicago team runs weekly schedule publications. When agents submit swaps via self-service, the backend hits the shift trading match operation. The JSON structure matches the schema, but the response indicates a conflict with the adherence rules engine. No specific field errors are returned in the body.