When a model is moved to the Archive

When a model is moved to the Archive

This page explains (in plain terms) when a model stops being “active” and appears in the Archive lists.

What “Archive” means

A model is moved to the Archive after it reaches an end state according to its monitoring rules. Archived models stay available for review, but they are no longer treated as active.

Typical reasons a model gets archived

A model is usually moved to the Archive when one of these completion events happens:

• The model reaches its Approach level (the expected approach occurs).
• The model hits its Loss/Stop level (a loss threshold is reached).
• A long-term break condition is triggered (if the model uses long-term checks).
• A final level is reached (for example, a “P6”/final step in the model’s path).
• One of the model targets is reached (Target 1–Target 4, depending on the model).
• A reverse / overrun completion condition happens (scenario-specific finish states).

Why “Time Depth = 100%” does not always move a model to Archive

The Time Depth indicator is a progress/age metric shown in the UI. It does not automatically archive a model by itself.

To be archived, a model must reach a defined completion event from the list above.

What to do if you think a model should be archived

• Check whether any completion event (Approach/Loss/Target/etc.) has actually been triggered for that model.
• If the model appears to be finished but is still active, report the model ID to support/dev team so they can review the monitoring rules and the model status.