So an uncaught error could de-rail all subsequent results. I'll have to look closer for un-caught errors

I've created a few batch jobs that run off of a custom record that details the process metadata and on occasion what data it processed. I had a really slick solution to detail data as a sublist item this one time and it allowed me to rollback issues if the process wasn't completed. If you REALLY need to know that the process runs completely you could do something similar to identify and fix any unforseen issues