At present, the system generates umbrella error messages that are generic and often not meaningful to end users, which complicates the troubleshooting process.

For example:

• “The selected report can’t be found. Make sure the report hasn’t been deleted, or work with your administrator to find the correct report. The report exists, but its data is missing. [An internal error occurred in the provider. An error occurred connecting to the source system.]
• ”

In one actual scenario, this error message occurs when there has been a change to operational data, such as a legal entity name change, which was not reflected in the financial report design (specifically the Reporting Tree definition). However, the current error message does not point users to the specific data they need to check, which prolongs the troubleshooting process and negatively impacts user productivity.

This becomes especially problematic in time-sensitive situations, where users need to generate a large number of reports quickly to avoid penalties. The lack of clarity in error messages leads to unnecessary delays and business impact.

To address this, we propose implementing more detailed and user-friendly error messages that can guide users directly to the issue, enabling them to identify and resolve problems more efficiently. Clearer messages would ultimately improve the user experience, reduce troubleshooting time, and mitigate potential business.

For example, when the legal entity name has been changed in the main system and the change has not been updated accordingly to the financial reporting tree, there should be an error like: "The report cannot be generated. Check the Reporting tree definition."