company

Admin Crashes Show What Broke — Not a Black Screen

The EEK admin portal was wrapped in an error boundary that displays the error detail, component stack, and a reload button. Bugs are visible and diagnosable the moment they occur.

29 April 20262 min read

When Something Goes Wrong, It Is Visible

Before the error boundary, a crash in the EEK admin portal produced a blank screen. The admin team would know something had broken — but not what, not where, and not how to diagnose it. In a live operations environment where the admin portal is the single view of all active jobs, a blank screen at the wrong moment has real consequences for customers waiting on updates.

The error boundary wraps the entire admin application. When a component crashes, instead of a blank screen, admin sees the error message, the component stack trace (showing exactly where in the application the crash occurred), and a Reload button to return to a working state. The crash is reported immediately rather than discovered when someone notices the screen has been blank for ten minutes.

Faster Recovery. Faster Service Restoration.

With the error details visible, the development team can identify and fix the underlying issue quickly. For the admin team, the reload button means a momentary crash does not take down the portal for minutes while someone works out what happened. The error boundary converts a disruptive outage into a brief, understandable interruption with a clear path to recovery.

Need help right now?

Our team is available 24/7 to help with misfuelling emergencies.

0800 769 000