Planner: inconsistent order status message

[katharinabassler]

In one production environment, it was observed repeatedly that an order was marked as failed (status) as well as queued for processing (status message), which should not be true at the same time. We were shown the following response from our /ProductionOrders(id) endpoint:

{
  "@odata.context": "$metadata#ProductionOrders/$entity",
  "Id": "<some-id>",
  "Status": "failed",
  "StatusMessage": "request is queued for processing",
  "OrderOutputSize": 0,
  "SubmissionDate": "<some-date>",
  "EstimatedDate": null,
  "CompletedDate": null,
  "EvictionDate": null,
  "Priority": 50,
  "InputProductReference": {
    "Reference": "<some-reference>",
    "ContentDate": null
  },
  "WorkflowId": "<some-id>",
  "WorkflowName": "<some-name>",
  "WorkflowOptions": [
    {
      "Name": "Dem",
      "Value": "coarse"
    }
  ],
  "NotificationEndpoint": null,
  "NotificationEpUsername": null,
  "NotificationEpPassword": null
}