Press CTRL+K to open search

Assessments Error Handling

  • Updated on Sep 1, 2026
  • Published on Aug 21, 2026
  • 5 minute(s) read
Prev Next

Error Codes — Assessment Task Troubleshooting

When an Assessment Task fails or is terminated, Matilda can open this page from Learn more so you can see what happened and what to do next — without digging through logs.

These codes apply to the Assessment Task as a whole (create → initiate → assess → TCO → report). They do not describe a single asset, host, or individual assessment record.

This page is for customers, CSM / Support, and anyone helping to unblock an assessment. Open it from the documentation link on a failed or terminated task in the Assessment list, or search for the code below.

How to read an error code

Every code uses this format:

MTL-ASM-<STAGE>-<NNN>

Example: MTL-ASM-TASK-012

Part

Meaning

MTL

Matilda product

ASM

Assessment module

STAGE

Where in the task lifecycle it failed or stopped

NNN

The specific issue (unique number in that stage)

Stage values you will see

Stage in the code

When it is used

TASK

Overall task failure or termination

INIT

The task could not start or dispatch work

BILL

Billing track failed for the task

TCO

TCO stage failed for the task

REPORT

Report could not start or could not finish

EXEC

Reserved for task-level execution dead-ends

What you will see in the product

  • The Stage column shows a short label such as Assessment Failed, TCO Failed, Report Failed, or AssessmentTerminated.

  • The message on that stage is the customer-facing explanation.

  • Click Learn more to open this page at the matching heading (for example #MTL-ASM-TASK-012).

  • Share the error code with Support if you need help.

When you contact Support, include:

  1. Assessment Task name or ID

  2. The error code (for example MTL-ASM-REPORT-002)

  3. Source and target cloud (for example GCP → OCI)

Fallback codes (always used when a more specific code is not stored yet)

Learn more is shown only for Failed and Terminated tasks. If a more specific code is not stored on the task, the link still opens a known article:

Situation

Code

Why this exists

Task is Terminated

MTL-ASM-TASK-012

The assessment was stopped and will not continue. Create a new task if you still need the work.

Failed task that existed before error-code tracking was released

MTL-ASM-TASK-998

This outcome was recorded before Assessment error codes were available. A specific cause and recovery path were not captured for this task.

Task Failed after error codes were released, and no specific code is stored yet

MTL-ASM-TASK-999

We do not have a more specific article for this failure yet. Contact Support with the task name or ID.

How to use this page

  1. Note the Stage label on the task (for example Assessment Failed or TCO Failed).

  2. Find the matching heading below — the heading is the error code only.

  3. Read What happened, then follow Next actions.

  4. Create a new task, re-initiate, or contact Support only when the next actions say to do so.

Assessment Task lifecycle error codes

Each heading is the code only so documentation links can be built as ...#MTL-ASM-TASK-012.

MTL-ASM-TASK-011

  • What happened: The assessment module reported that this Assessment Task failed before it could finish.

  • Next actions:

    1. Read the Stage steps (Precheck / Assessment / TCO / Report) to see which step failed.

    2. Re-initiate failed assessments when that action is available; otherwise create a new task.

    3. Contact Support with the task name or ID and MTL-ASM-TASK-011 if it fails again.

MTL-ASM-TASK-012

  • What happened: This assessment was stopped before it finished. A terminated task does not resume. This usually happens when someone stops the assessment on purpose.

  • Next actions:

    1. Create a new Assessment Task if you still need this assessment.

    2. Do not wait for this task to continue — it will stay Terminated.

    3. If you did not mean to stop it, contact Support with the task name or ID and MTL-ASM-TASK-012.

MTL-ASM-TASK-013

  • What happened: An account or company included in this Assessment Task was deleted from User Management. Matilda removed the deleted account configuration, so the original task scope changed and the task was marked Failed.

  • Next actions:

    1. Read the task message to confirm which account or company was deleted.

    2. If accounts remain and Reinitiate is available, choose Complete re-initiation. The new task will include only the remaining accounts.

    3. If no accounts remain, create a new Assessment Task after adding or selecting a valid account.

    4. Contact Support with the task name or ID and MTL-ASM-TASK-013 if the deletion was unexpected.

MTL-ASM-INIT-002

  • What happened: Matilda could not start this assessment because communication with the assessment module failed (for example HTTP error, timeout, or an invalid response).

  • Next actions:

    1. Wait a few minutes and re-initiate the task if that action is available.

    2. If it fails again, contact Support with the task name or ID and MTL-ASM-INIT-002.

MTL-ASM-INIT-003

  • What happened: Required files for this assessment could not be stored, so initiation was stopped. The Assessment Task did not start.

  • Next actions:

    1. Confirm the uploaded file is valid and try creating a new Assessment Task.

    2. If upload fails again, contact Support with the task name or ID and MTL-ASM-INIT-003.

MTL-ASM-BILL-001

  • What happened: The billing track for this Assessment Task failed. This is a task-level billing failure, not a single asset.

  • Next actions:

    1. Confirm the billing file or billing source is valid, then create a new task or re-initiate if that action is available.

    2. Contact Support with the task name or ID and MTL-ASM-BILL-001 if billing fails again.

MTL-ASM-TCO-001

  • What happened: The TCO stage for this Assessment Task failed (for example supplemental TCO such as ROSA or NetApp could not complete for the task).

  • Next actions:

    1. One account failing TCO in a multi-account billing task does not use this code — that is recorded as a partial TCO comment and the task can still continue to report.

    2. If the Stage column shows TCO Failed, contact Support with the task name or ID and MTL-ASM-TCO-001.

    3. You may create a new Assessment Task if you still need a complete TCO result.

MTL-ASM-REPORT-001

  • What happened: Report generation could not be started for this Assessment Task (the report service did not accept the request).

  • Next actions:

    1. Retry report generation if that action is available.

    2. Contact Support with the task name or ID and MTL-ASM-REPORT-001.

MTL-ASM-REPORT-002

  • What happened: Report generation started but did not finish successfully for this Assessment Task.

  • Next actions:

    1. Retry report generation if that action is available.

    2. Contact Support with the task name or ID and MTL-ASM-REPORT-002.

MTL-ASM-TASK-998

  • What happened: This assessment failed before Assessment error-code tracking was available. Because this result was recorded before that capability was released, a specific cause and recommended next steps were not captured for this task.

  • Next actions:

    1. There is no scenario-specific recovery procedure for this historical failure.

    2. If you still need this assessment, create a new Assessment Task, or use Reinitiate if that action is available for this task.

    3. Contact Support with the Assessment Task name or ID and MTL-ASM-TASK-998 if you need help reviewing this older result.

MTL-ASM-TASK-999

  • What happened: This assessment failed, and we do not have a more specific troubleshooting article for this case yet. That does not mean the work is lost — it means Support needs the task details to investigate.

  • Next actions:

    1. Note the Assessment Task name or ID and which stage failed (Precheck, Assessment, TCO, or Report).

    2. Contact Support with that information and MTL-ASM-TASK-999.

    3. Do not keep retrying until Support confirms it is safe.

Related articles