Oh yes I am sorry; I didn't mean to imply that I thought that the DB was throwing an error. What the filing process email message body stated looked something like approximately "Form line xxx violates schema requirement such and such: <more gibberish>".

I was thinking when I scanned the message was that I bet I could reverse engineer the problem from this back end generated text but why not do what the instructions say and just feed it into the parser box? And every time the next email message gave me exactly the thing I needed to do. It was cool, for a weird sort of nerd.

So no, I was casting shade where the process was right in the sunlight: I made the mistake, and the business logic caught it, and told me correctly every time what I needed to do to fix it. I liked the whole process a lot.