Un-necesssssary, as not only are you running multiple projects, so at least one of them will have work available at any given time, but the server issue here isn't one affecting work availability.

People keep suggesing this. I am signed up for six projects and Rosetta and WCG are the only ones that send out work. And in the past, WCG was nearly down for about two years, so does it count? And ClimatePredicion does not send me Linux work in many months and their web site is currently down..

---

At least it wasn't human life support system.

I haven't completed any tasks from the new batch yet, but I just checked anyway.
I haven't had any tasks crash early in their run from anything I've downloaded in the last 40hrs.
That'll be tasks from previous batches of work in the main, but let's cross fingers that it also applies to the 2.2m batch as I estimate we lost around 25% of tasks from the previous one.
That's a lot of work and a lot of extra time we could've been running - maybe 2-3 days worth.

I've just realised it's not dependent on whether I've completed tasks from the new batch but whether I've started any.
None of the 6 new batch tasks I've started have crashed out early, so that's a positive start.

13 now and the first of the new batch wlll finish in about an hour too.
Looks like they solved those task errors

---