Does anyone have an explanation for why a WU being reissued after a "Timed out - no response" is sent to two different computers within 10 seconds. It would appear the first computer to respond receives credit but the second remains as "pending".

An example WU is 1116808887.

I did a search on what I thought were the keywords and came up empty. If I missed the explaining thread, a pointer would be good enough.

Does anyone have an explanation for why a WU being reissued after a "Timed out - no response" is sent to two different computers within 10 seconds. It would appear the first computer to respond receives credit but the second remains as "pending".

An example WU is 1116808887.

I did a search on what I thought were the keywords and came up empty. If I missed the explaining thread, a pointer would be good enough.

Simple, tasks 0 and 1 were late, so tasks 2 and 3 were sent, (task 1 was propably a resend to that's why there's a 3 day difference in send time/date)

Task 1 then arrives late, and validates against task 2 when it arrives too, task 3 is too late to validate, and is likely to sit in limbo until someone fixes this validator Bug,

Claggy

Does anyone have an explanation for why a WU being reissued after a "Timed out - no response" is sent to two different computers within 10 seconds. It would appear the first computer to respond receives credit but the second remains as "pending".

An example WU is 1116808887.

I did a search on what I thought were the keywords and came up empty. If I missed the explaining thread, a pointer would be good enough.

Simple, tasks 0 and 1 were late, so tasks 2 and 3 were sent, (task 1 was propably a resend to that's why there's a 3 day difference in send time/date)

Task 1 then arrives late, and validates against task 2 when it arrives too, task 3 is too late to validate, and is likely to sit in limbo until someone fixes this validator Bug,

Claggy

Got it. It never occurred to me that both computers that were first sent the task had timed out. Thanks.