Yup, I noticed that and wondered about it -- it makes some sort of sense if there's a current bias towards laggards of various types, but I'm not sure whether that's by accident or design!

It appears that at present only laggards of various degree are being sent out -- if we still have the "6 generations are leading generations, anything two or more behind is laggard" definition in place, 130..135 are leading, 127 and earlier are laggard (and, of course, 125 and earlier were already tagged as Accelerated or Extreme...)

I've ploughed through Kevin's posts over the last year or so, trying to get more clarity; there are references to various conditions, such as

• not releasing a new generation until it has at least 350 units ready to go
  
• the number of generations considered "leading" (currently seems to be 6)
  
• how far behind the leading generation(s) one needs to be to be considered laggard
  
• when a generation should be "Accelerated" (which doesn't always seem to match the definition of laggard...)
  
• when a generation should become "Extreme" (that used to be 25 behind...)
  

but I couldn't find anything consistent and relatively current :-(

I don't know how much of the generation control and task delay was manual and how much was automatic... i also wonder how much effect some of the last-minute tinkering to get a stable state for transition with no work outstanding might've had on how work release might behave now we've a [partial] restart... Pure speculation, of course; if there was anything definitive posted about this, I missed it!

Now, if someone can educate me on what I'm missing, I'd be delighted to learn :-)

Cheers - Al.

Great summation Al. - thanks.

I just got a resend, and I was curious if anyone is getting any new WUs or if we are just seeing resends at this point.

Do they need to test the TB project still? or did I miss it since it is so small? I wonder what is next on the test list before we are back??

There has been no movement in generations up to 100 in the last day. A few have moved up a generation between generations 101 & 120 and a number between 121 & 127.

Mike

Got an ARP1_100 about 90 minutes ago.

That WU, was ARP1_0012662_125

And the results are:

ARP1_0012662_125_0 Error
ARP1_0012662_125_1 No Reply
ARP1_0012662_125_2 Valid
ARP1_0012662_125_3 No Reply
ARP1_0012662_125_4 Valid

So, I did return my _4, and everything is fine with ARP1_0012662_125 now.

Edit, added: And just now I received 3 more tasks, thank you very much WCG
ARP1_0019670_127_1
ARP1_0025295_127_0
ARP1_0025307_127_1

Download struggle as ususal, with lots of "transient HTTP error", but nothing that some manual crazy button clicking can't handle