part of the madness comes from pausing a WU for a prolonged period. Start it on day 1 crunch a few hours, do a few hours more the next day, than do the last few on day 3. BOINC will perceive u only crunching 6 hours for that project in 2+ days..... sort of the simplified explanation. It's all designed to ensure that u 'never' end up with a work buffer volume that can not be finished within the schedule. Running 5.8.1 now (not a production approved version) and all was in balance until a 10 CPU hours FA@H came along.

No, it's not going to keep me awake..... no itches, just letting it do the job.....sooner or later it will fetch new work.... oh and suspending WU's no longer forces new work retrieval in the 5.8.x series. BOINC knows they are there :O

Please post the WU name and the device/computer ID or send in email form to 'Contact Us', so the technicians can have a look. What were the results of the others in the quorum for that WU (see Result Status page and click on the WU name).

plz review your message tab / log file for any entries of the subject WU and post them/mail them too.

Kevin,you aren't kidding!!! TC times on FAAH have dropped by one third and FCG by two-thirds. Now those may go up a little once the previous WU's work out of the queue.

Nothing to worry about: this is a predictable consequence of adjusting the estimates. It will normalise quickly.

Yep, I noticed that too. My TC times have doubled since my last post. I presumed that was some sort of consequence of the change and I figured I'd wait until the pre-change WUs are out of my queue to see how things look then. As it is, the post-change WUs have TCs that appear to be much more accurate.