Run results and consistency with the audit trail
Milliman Mind provides real-time information about the consistency of the results produced by the latest run with the current state of your project.
This information can be seen thanks to the background color of the run button in the Action bar on the left of your screen.
Four different states can be seen:
![]() |
![]() |
![]() |
![]() |
|
No results Your project does not have any results produced by Mind. It is the status after your models upload. |
Results consistent Your calculated results are consistent with the current status of your project and its audit trail. |
Results consistent up to an earlier change Your calculated results are inconsistent with the current state, but consistent up to an earlier audit trail entry. |
Results inconsistent Your results are not consistent with the audit trail, meaning some external changes have been merged in between two changes on your session. |
Run to update the consistency status of your results
After a full run of your Milliman Mind project, the results become automatically consistent with the audit trail because a run takes all your changes (and also others) into account to calculate the results. Your run button will then become Green after each complete calculation process.

Any change in your project will change the consistency status
If you change your model, for example by importing an input or changing an assumption (any change logged in the Audit trail impacting the calculations), the results of your project will become incoherent with the latest changes and the run button will turn Orange. The status of the consistency of the result will then be "Coherent up to <A specific date>", meaning it is still coherent except for everything related to the changes more recent that the latest run.
If you run again your model, the latest changes will be taken into account and your results will become fully consistent again.

Saving the results of your projects
You can only save results that are consistent with the project (Green run button). If the button is Red or Orange (inconsistent), a warning pop-up will ask you to save without results.
This behavior has been decided to prevent save of results that would not be consistent with the latest changes.
Result consistency status for partial load
- If at least one instance group has no results when you Load all the consistency status is No run.
- If at least one instance group is inconsistent when you Load all the consistency status is Inconsistent.
- If at least one instance group has been run separately from a Run all and is "Consistent" or "Consistent up to X", then when you Load all the consistency status is in a new state: it is orange with the message "Instance groups are self-consistent".
Parallel work on the same project
The consistency mechanism also improves teamwork capabilities to work in parallel on the same project.
The audit trail is now merged in real-time when 2+ people work on the same project at the same time.
When a user has unsaved changes in their audit trail, and this user clicks on the save button, it will automatically propagate the new changes to every user with the same project open on a matching scope (same instance group selected or project open as All).
All other users will then get a notification and a new indicator on the audit trail button, showing them that new changes are available but have not been merged.

To merge these changes the audit trail of the current session, the user has two choices:
- Either go to the Audit trail, then click on the Merge button.
In this case, their current results will become either Consistent up to X or Inconsistent.
- Or run the calculation because changes are automatically merged before each run.
With this mechanism, the audit trail is always up to date, and you are updated in real-time with new changes and their impacts on your results.
Audit trail of run and consistency
The audit trail of run shows the consistency status of each of your runs, giving you feedback on when was run a set of data, and this can be easily crossed with the audit trail of changes to know when a set of data was created.




