General error troubleshooting

This article covers what to do when MakrPrep shows an unexpected error.

Before you start

None.

Steps

If a screen shows a broken/error state, MakrPrep's error boundaries should keep the rest of the app usable — try navigating to a different screen and back.
If an action fails (e.g. saving an edit), look for a toast notification describing the server error.
Refresh the page if a screen seems stuck without any visible error.
If the problem persists, note what you were doing right before it happened (which screen, which action) — this is the most useful detail for tracking the cause down.

What to expect

Most errors surface as a toast rather than a blank or broken screen — MakrPrep is designed so one failed action doesn't take down the whole app.

Error toast appears but the action seemed to complete anyway — check the actual data (e.g. did the edit save?) rather than trusting the toast alone; refresh to confirm current state.
Same error keeps happening on one specific screen — this is worth reporting directly rather than working around, since a repeatable error usually points to a real bug.