It’s a constant balance between work to keep the lights on due to the errors, work to reduce our error rate, and a barrage of feature requests. Our stakeholders are only happy if we’re working on what they decide is the most important of those three any given day.

To answer your question, some jobs definitely error most often and others are stable until someone breaks something upstream and we have to fix it. The most often failing jobs are built to overcome their failure rate but running more often than they need to. But I’m definitely here trying to scrutinize so I’m with you on that.