Error Insights

Problem Statement
There is big room for IBM to improve the text associated with the internal error messages, such as the 404 error and 500 error. Currently, error messages in MIO provide limited guidance on the underlying cause of the issue. As a result, users are often unable to take corrective action independently and must rely on Support tickets to move forward.

Ask
While providing a full root cause analysis for every error may not be feasible, there is a clear opportunity to enhance error messaging with actionable, contextual guidance for common and well-understood scenarios. This would significantly improve user autonomy, reduce dependency on Support, and accelerate issue resolution.

Proposed Enhancement
Enrich error messages with targeted, user-friendly insights and suggested next steps for common failure cases, such as:

• Missing prerequisites required to run recalculations
• Missing or outdated input files
• Ongoing refresh processes blocking calculations
• Incomplete commitments preventing workflow finalization

Scenario 1 - Nothing that the end user can do to avoid the error: 

In this case, the ask is to provide an explanation of why the error is happening

Scenario 2 - the user can avoid the error:

In this case, the ask is to provide an explanation and a course of action.

An example is the error that occurs when somebody is trying to log in with a shortcut they saved from within MIO ... it seems that it only works for an initial login from the root web address, but this is not clear from the error message pop up box. 

Another error that raises a lot of questions from users is the ERO error since it blocks the user from approving an item.  Perhaps more text could be added to the ribbon at the top of the screen that displays this error - it would be useful if it explained that the Lead Time is too long.  Also it seems like it is impossible to clear this error by decreasing the usage rate, which theoretically should work.