Project 16815, Timeout is zero

[Maddog]

Hello, just got this project assigned a short while ago and the timeout is exactly the same as the assign time.
Checking the project summary shows the timeout is set at zero.
This seems to be a problem, because checking the WU status( 16815,10,626,49) shows that this WU has been issued twice, before being assigned to my machine, and
was assigned 29 minutes before the previous donor had returned it.

[bruce]

You're observing a relatively new change called "dynamic timeouts"

The original timeout is set by the project owner based on benchmarking prior to the WU being issued. After that, the server can adjust the timeout to prevent the initial assignee from being "too slow"

Setting it to zero was an error which has been corrected.

[BobWilliams757]

I must have got one when it was in limbo. It reported as super slow on HFM for my machine. When I checked on WU status it actually gave me a return in line with my CPU folds, but maybe the reported timeout when I picked it up threw off HFM. Being that it reported as the lowest PPD ever on my machine, it was easy to spot.

Good to see it's already fixed either way.