p17925-r24-c86-g0

[Mactin]

p17925-r24-c86-g0 has had 130 failures since May-27. Almost all from different donors.
Funny thing, the logged credits show it succeeded over a year ago on 2024-07-03.

A few WUs before :
p14972-r0-c88-g9, according to logged credits, folded successfully on 2024-04-18 (15 months ago);
failed with another donor on 2025-07-29 (yesterday);
then thirdly, I processed it OK on the same day.

Under what circumstances a successfully folded WU get re-issued for re-folding (with such a time gap) ?
Why would it fail to fold the 2nd time ?

[muziqaz]

When server starts bugging out, or researcher messes up with some scripts

[Mactin]

I had another one :
p14972-r0-c116-g11, folded by user satellaview, team 223518, for 105000 points on 2024-04-19 00:30:34

Please let the researcher know.

Edit 15 minutes later
before it : p14972-r0-c-89-g18 (previously processed 24-04-20)
currently folding : p14972-r0-c28-g10 (folded 24--04-17)

If this is an error, it is a waste of donor resources ! Fix it soon !

[muziqaz]

The fix has not been applied yet.

[muziqaz]

In regards to 17925:

I think I know what is the reason for this. This is an old project that I restarted recently to get more data. When the server was going through the issue of huge amounts of failed WUs from the user Damage, i added the setting </clear-job-errors>, which would resend the failed units for folding. I did not change the setting when added another round to this project recently. The failed WU in the post could be a genuine misfolded state which would fail everytime, and whenever the assignment server is restarted, it sends out all failed WUs, including the misfolded ones, which are bound to fail again.
14:42
I will change the </clear-job-errors> so the old failed WUs should not be sent out

Still waiting for the fix for 14972

[Mactin]

Another update :
I am currently processing p12130-r1-c36-g20. It was previously folded last week (25-07-23).