So 24 machines all with 2x long2 running with 4 to 6 days of computation time into each WU (BOINC decided to swap WU at 70-90% completion to a new WU, might have to change switch between tasks to 9999 minutes).

Some drunk driver ran into a main electric line pole and dropped it on a house setting the house on fire. Plunged 4000 homes into darkness. I'm 2 miles away and just got 2 spikes, taking down all the machines (no, I can't afford battery backups).

Long2's all report 0% completion. Due dates of 4/21.

So, how sure are you that these WU's all restarted from the save points of 80-95% completion?
If they start completing over the next day and swapping back to the other unfinished then everything's fine. But if they keep going for 3 more days
they are starting completely from scratch?

Please reassure me as it seems like 200+ CPU days of work is kaputt(one of the few German words grandma taught me that wasn't filthy).

let the first one run, the pause it manually for a short time, that the second can run.
then press right click onone of the tasks, then press, i think in english it is properties, and look in which slot the task is. open the folder of this slot and look what progress your stderr.txt file says at the bottom. this is the progress from which the task (should) restart

Thankyou for the responses.

Wasn't hard to find the right slot director(ies); it's the ones with llr.exe in it.

The one machine ended at 80.44% and is now at 90.28% so that WU is fine. I'll check them all.

(You all told me how to do this 3 months ago and I forgot. Everytime I have a major depressive episode; there seems to be memory loss.)

These long2 are set to -t3 from earlier data set I collected and that isn't enough threads for the downclocked fall/spring CPU timings.

Changing to -t6 like the long1's.