I agree, thereโs no point in getting the email alerts if youโre just going to filter them out. Itโs like turning down the fire alarm because you donโt like the sound. I want to be notified of the errors, I just donโt want to have 40 emails for one error.
More generally, the error handling system doesnโt make sense. If an error occurs:
- the users arenโt alerted and donโt think anything is wrong.
- all of their subsequent changes to the app get lost.
- The only way to fix the errors is to reset the changes which writes all of those errors in JSON to text files <โโ this also makes no sense. If itโs written in JSON it should write it to a JSON file, not a text file.
- I digress
- I receive 90,000 emails about issues I canโt fix without getting in touch with the user and asking them to reset their changes.
It would make a lot more sense if it automatically reset the change, wrote it to a recovery json file and present an error message modal to the user โYouโre change was not saved due to a technical issue. Your administrator has been alertedโ.
That way the users donโt lose all of their work and they arenโt surprised when they see something missing. App owners donโt get a tidal wave of emails and, instead get one email with a json file attached that they can use to fix the problem.
LinkedIn
Twitter
