Work Running 100% Of Time Despite Settings?

Has anyone else seen this? I've been away from Einstein for a while and just got my first batch of work units, which although they have a deadline weeks away are running 100% of the time, i.e. not suspending after 60 minutes to allow other projects to go, despite my settings to the contrary.
It's not a dire problem, but am curious as to why it would happen.

The new CPU + GPU scheduler and work fetch module
OK, now, you have by now noticed that your old BOINC 6 did things differently than this BOINC 7.0 does things. That's because the old 6 was deemed broken and the new 7.0 is deemed fixed, but with some bugs still included.

The REC-based scheduler
What the client does is, it keeps a record of how much CPU/GPU time a certain project has recently seen - the recent estimated credit (REC). It compares this figure with the project share that has been set. A project that has worked less than its share will get priority in both scheduling (running tasks) and work fetch. Then as it gets crunch time its REC increases and another project will get to the head of the queue. Over time you get a more or less good distribution of crunching time according to resource share.

Points of note:
- GPUs are very productive so lead to high REC. If you run GPU projects alongside CPU ones on similar shares the GPU project sees virtually no CPU.
- CPU and GPU are scheduled separately.
- A project like SETI will probably stay pretty high up in the queue, since getting tasks is hit and miss due to their bandwidth being overworked.
-- However, setting a small 'additional days' cache will help getting tasks from Seti, since BOINC will ask more often, thereby increasing your chances.