Currently, when an error occurs in the web application, the error message shown to the user is very generic and does not provide enough detail to understand the root cause. To properly analyze the issue, users must manually access the server and inspect log files.
In a recent case, the issue was caused by missing folder permissions that were only granted to a subset of users. This was not visible from the web error message and could only be identified after checking the logs and coordinating internally with a colleague.
This workflow is time-consuming, inefficient, and error-prone—especially for recurring or minor configuration issues. As a workaround, users repeatedly access log folders on the server, which interrupts the troubleshooting process and requires additional technical access.
How often is this impacting your users?
Frequently.
This occurs whenever configuration, permission, or backend-related issues arise, which is a regular part of day-to-day operations and development work.
Who is this impacting?
- Model builders
- Solution architects
- Administrators
- Integration experts
- Technical consultants
- Advanced business users with troubleshooting responsibilities
Ideal Solution / Value Added
The ideal solution would be an optional, configurable way to display more detailed error messages directly in the web interface (e.g. via a “Show technical details” toggle or debug mode).
This could include:
- The underlying error message
- A short technical description
- A reference or correlation ID that links directly to the corresponding log entry
This would significantly reduce troubleshooting time, minimize unnecessary server access, and improve overall user efficiency. It would also make the system more transparent and user-friendly for technical users, while still allowing generic messages for non-technical end users.
