Discussions

Ask a Question
Back to all

WoCreateCommand returns "assignment is required" even though Assignments array is provided

I'm calling the Corrigo api/v1/cmd/WoCreateCommand endpoint directly with the following JSON payload:

{
"Command": {
"WorkOrder": {
"TypeCategory": 4,
"SubType": { "Id": 259 },
"Customer": { "Id": 4 },
"ContactName": "Deyu Zhu",
"Items": [
{
"Asset": { "Id": 493519 },
"Task": { "Id": 14879 },
"Comment": "1111"
}
],
"ContactAddress": {
"AddrTypeId": "17",
"Address": "[email protected]"
},
"Assignments": [
{
"isPrimary": true,
"EmployeeId": 2754
}
]
},
"ComputeSchedule": true,
"ComputeAssignment": false
}
}

The response is:

{
"ErrorMessage": "Priority 'P4-Standard' is escalated; assignment is required",
"ErrorCode": "ERROR_CODE_1",
"TimeStamp": "2026-08-11T00:33:01.3594249Z"
}

I have a few questions about this:

  1. The Assignments array is present with an EmployeeId of 2754, and isPrimary is set to true. Why does the API still
    say "assignment is required"?

  2. Should ComputeAssignment be set to true instead of false? Or does ComputeAssignment control whether the system
    auto-assigns based on schedule, meaning it should be false when manually providing assignments?

  3. Is the JSON property name isPrimary (lowercase 'i') correct for the assignment object, or should it be IsPrimary
    (PascalCase) to match the Corrigo API convention?

  4. Are there any required fields in the Assignments entry that I might be missing? The WoAssignment entity in the SDK
    also has Id and WorkOrderId fields — are these required when creating a work order, or are they only populated on
    read?

Any guidance on the correct format for passing assignments in WoCreateCommand would be appreciated.