when something would fail to save, it would shake the screen and light up in red the box that wasnt saved yet, something like discord does
Please add this 
When are things failing to save?
when a user tries leaving the current block while something is saving or failed to save
Saves should happen asynchronously in the background even after page navigation. I don’t see how blocking page exits for saves helps here.
If you’re regularly losing data navigating off flow pages, that’s a separate issue and should be filed separately. This wouldn’t really fix that anyway.
In Discord’s case, they require manual user action for saves and shake the screen when you forget to save before navigating off. We don’t require user action for saves so this doesn’t really make sense.
Like if you have input errors (the Discord regex) maybe, that’s what I was thinking
When you enter invalid data it is still saved. You just get a warning that it isn’t valid.
I’m going to close this because it doesn’t address an actual issue. If you are regularly losing data, open a bug report with reproduction steps.