Explain why maintenance mode was activated and what needs to be done

Admins want to see a clear reason and actionable guidance when the system enters maintenance mode automatically, so they can resolve the underlying issue quickly without having to investigate everything from scratch. Problem / Pain: When the system activates maintenance mode automatically, for example because an app could not be loaded due to a dependency issue or because an update script did not complete, admins are not told why. The system is in maintenance mode, but there is no explanation of what triggered it or what needs to be done to resolve it. In the worst case, admins have to review everything that was recently changed or updated to find the root cause, which is time-consuming and stressful in time-sensitive situations. Impact / Benefit: A clear explanation of why maintenance mode was activated, combined with guidance on what action is needed, would allow admins to resolve issues significantly faster. It would reduce unnecessary investigation effort, lower the risk of missing the actual root cause, and give admins the confidence to act decisively rather than having to work through every possible cause by trial and error. Example use case: An admin arrives at work to find the system in maintenance mode. Currently they have no idea what triggered it and must start investigating from scratch. With a clear maintenance mode explanation, they would immediately see that a specific update script did not complete along with guidance on what to do next and could resolve the issue directly without further investigation. Idea source: Internal suggestion Voting note: Vote for this idea if this need is relevant to you as well.