And while at it, untick "disconnect when done", only really of use for folks on very restricted bandwidths who need to carefully control when and how much they transfer.Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Try setting it to something like 3 + 0.01 for now, and see if you get any work resent,

The first setting fulfills the low water mark for your Cache, it also fulfills the 'how many days offline' you're going to be, so any work with short deadlines will be bumped to the front of the que to be done first, like that shortie you completed yesterday,

The second setting fulfills the High Water mark for your Cache, Boinc will fill to your Low + High Water marks then wait for the Cache to go under the Low Water mark before asking again, this might be why it won't ask for work at the moment,

Another thing to try is a later Boinc, Boinc 7.0.34 had some important work fetch changes:

client: when we're making a scheduler RPC for a reason other than work fetch, and we're deciding whether to piggyback a work request, skip the checks for hysteresis (buffer < min) and for per-resource backoff time. These checks are there only to limit the rate of RPCs, which is not relevant since we're doing one any.

This fixes a bug where a project w/ sporadic jobs specifies a next_rpc_delay to ensure regular polling from clients. When these polls occur they should request work regardless of backoff.