Minor issue. Plenty of other seti 7.7 tasks that are due 3 days earlier and two tasks are due a 32 days earlier.

Tasks always run in the order they were issued, not in deadline order.

Sometimes if a block of tasks are allocated at the same time, a task in the middle of the block can complete its download first and start running (if a device is idle). But once all downloads are complete, the tasks should be processed in order from the top down (if you have the 'native' BOINC Manager display, with no column sorting applied).

A couple of issues with your post.

a) It's not a BOINC Manager problem, as it's not BOINC Manager that dictates what runs when, but the client that does so. BOINC manager is just a graphical user interface that shows output of what the client does and makes it easier for you to control the client.

b) BOINC 7.1.1 is a development client. Not even a release candidate development client, but an alpha client. Any problems you have with it, I prefer you post it directly to the developers, who can be reached on the appropriate Alpha email list. Please read the disclaimer as to why I prefer you post directly to the alpha email list, before you yell at me and angrily stomp off. The recommended (non-alpha, non-development) client can be downloaded from here.

c) Evidence. It's far easier for the developers to fix problems when you send message logs with the appropriate flags set. The main flags are:

<cpu_sched_debug>: problems involving the choice of applications to run.
<work_fetch_debug>: problems involving work fetch (which projects are asked for work, and how much).
<rr_simulation>: problems involving jobs being run in high-priority mode.
<sched_op_debug>: problems involving scheduler operations and other low level information.

In this case, add a log of a couple of minutes of <cpu_sched_debug> and one of <rr_simulation>

d) Seti v7 (not 7.7) has only been released yesterday. It uses brand new applications and work. All the before-known variables about how long work used to do on v6 went out of the window, BOINC has to learn anew how long tasks take for v7. Allow it the ability to learn.

e) But even then, BOINC has always worked on a first in, first out basis. It doesn't look so much to do work based on its deadline, it tries to do all work before the deadline. Therefore work with an earlier deadline can easily be done at a later date than work with a later deadline. This has not changed in 7.1.1

---