Hi zxcvbob, if this is only happening on your laptop (which, I may be wrong, but I'm assuming you're only using on a part-time basis), could well have a "too high" buffer setting. When this happens, more WU's flow into it than it has time to complete, thus the "high priority" jobs.

What you might like to do, is to simply lower your buffer, as normally, WCG is pretty resilient to outages, thus, by having a .5 day buffer, that would get you over any potential outages that may occur.

As all the WCG WU's have at least a 7 day return buffer (that is, except for urgent "repair" WU's), this should give your machine plenty of time to crunch through them without setting BOINC into a panic status.

I have both Minimum work buffer and Max. additional work buffer set to 0.5. It is set the same or a little deeper on the other two computers. I am having long-running tasks (like Clean Energy Phase 2) occasionally download the same day they are due with not nearly enough time to actually run them even tho' they push their way to the top of the queue.

I'm OK with that if the deadline is extended at least 24 hours past what shows up in boinc manager. But if that's the case it should say so.

The 3 computers are all running a little different version-levels of boinc, I wonder if that makes a difference?

Thanks for listening.

That might be the version I had.
I upgraded the laptop last night to 7.2.33(x64). When I started it up I got a warning that one of the running tasks was overdue... so I just aborted it. Hopefully that will put me on some kind of WCG blacklist and they won't send me high priority tasks with short fuses (or no fuse) again.

I'm running version 6.10.58 on my office computer (I just checked) and it works great. I didn't realize it was that backlevel.

Maybe I should look for a copy and put that on the laptop.