Error codes
Model changes and the portfolio
Each code of this family: what it means, its most frequent cause, what to do and who can do it.
reference_set_not_found
- What it means
- This mandate has no reference set yet.
- Most frequent cause
- No reference cases were saved for the system.
- What to do
- This mandate has no reference set yet.
- Who can do it
- An owner or admin of the workspace · Open the screen
run_not_found
- What it means
- This comparison run does not exist in this workspace.
- Most frequent cause
- A link from another workspace, or a run id typed by hand.
- What to do
- This replay does not exist in this workspace.
- Who can do it
- Any member of the workspace
report_not_found
- What it means
- This comparison run has no report.
- Most frequent cause
- The run did not finish.
- What to do
- This replay has no report (it did not finish).
- Who can do it
- Any member of the workspace
not_a_candidate_run
- What it means
- Only a comparison run of a new model version can be acted on.
- Most frequent cause
- An action on a run of the version already in service.
- What to do
- Only a replay of a new version can be acted on.
- Who can do it
- Any member of the workspace
nothing_to_pin
- What it means
- There is no other version to route the calls to.
- Most frequent cause
- A routing asked without naming a model, while a single version was seen.
- What to do
- There is no other version to route to: name the model.
- Who can do it
- An owner or admin of the workspace
unknown_case
- What it means
- A case of the client receipt is not in the reference set, or its hash differs.
- Most frequent cause
- The reference set changed on the client side after the run started.
- What to do
- A case of the receipt is not in the reference set, or its hash differs.
- Who can do it
- The developer of the calling code
duplicate_case
- What it means
- The client receipt names a case twice.
- Most frequent cause
- A bug in the code that builds the receipt.
- What to do
- The receipt names a case twice.
- Who can do it
- The developer of the calling code
incomplete_receipt
- What it means
- The client receipt does not cover every case of the reference set.
- Most frequent cause
- Cases that failed on the client side and were left out.
- What to do
- The receipt must cover every case of the reference set.
- Who can do it
- The developer of the calling code
run_not_awaiting_client
- What it means
- This comparison run is not waiting for a client receipt.
- Most frequent cause
- It ran at Azoth, or its receipt was posted already.
- What to do
- This replay is not waiting for a receipt.
- Who can do it
- The developer of the calling code
month_in_future
- What it means
- The month asked has not started yet.
- Most frequent cause
- A month picker left on a month to come.
- What to do
- This month has not started yet: pick the current month or an earlier one.
- Who can do it
- Any member of the workspace
alternative_not_priced
- What it means
- The alternative model has no price, or is the model already in service, so no comparison was queued.
- Most frequent cause
- A model Azoth’s catalogue does not price, or the same model chosen twice.
- What to do
- Choose a priced model other than the one in service.
- Who can do it
- An owner or admin of the workspace · Open the screen
catalog_version_invalid
- What it means
- A version of the model catalogue is a number, or latest.
- Most frequent cause
- A version asked for with another word.
- What to do
- Ask for a version number, or latest.
- Who can do it
- The developer of the calling code
catalog_version_not_found
- What it means
- No published version of the model catalogue has this number.
- Most frequent cause
- A version not published yet.
- What to do
- Ask for latest, or for a number that was published.
- Who can do it
- The developer of the calling code