The Model already does roll-backs for internal errors. If it hits a brick wall, it rewinds a Model day and retries. If it still doesn\'t get through, it rewinds a Model month and, finally, a Model year before crashing.

External things are another matter entirely and can come from anything from hardware problems, to operator error, to program mix. For example, Norton anti-Virus scans can cause conflict if it happens to lock a file for scan just as CPDN wants that file. (For that reason we recommend that the CPDN folder be excluded from scans.) Can it be programmed? Perhaps. But it seems a complicated problem to trap & evaluate all the possibilities; meanwhile, Carl and Tolu have more than they can handle keeping all the Projects afloat.

What were the symptoms of your crash?

Edit: Regular backups of the entire CPDN folder are also recommended, to prevent that which you experienced. (Such a backup saved one of my Spinup Runs ~195 years into a 200 Model-year Run...)