Yes, you've activated log flags used only under instruction of someone who knows ;o). (I Think) they mean that it's WCG's turn to fetch work based on the momentary work share "shortfall", but you left the context lines before and after out as to what the client is doing. For a discussion see https://boinc.n-helix.com/forum_thread.php?id=9221 when the technical person starts with, yes, a warning. Also https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3741 . The last post is funny.

OK, re-found the wiki: https://boinc.berkeley.edu/trac/wiki/ClientSched

OK, so now this is 'the interpreter' thread. So Alged has a buffer bigger than the allowed runtime which is seemingly only 15.6 percent (maybe the client pauses a lot due user activity). BECAUSE, no new work will be assigned as it wont finish in time. E.g. 15.6% of a day is less than 3.7 hours, but if the computer is on only 8 hours a day, then 15.6% is 1.2 of real computing a day. 3 solutions,

1) leave the computer on longer,
2) allow computing while using,
3), cut the buffer further. With only few hours of actual computing a day, the buffer should really be zero to get anything finished in time.

All a big guess without knowing settings and up time profile.

As for your log cut off, the complete line is most probably in the stdoutdae.txt file.

Hi lavaflow ! thks or yr help
I apply this advice mainly points 2)&3) its getting better.
regards

Nous sommes tous des chercheurs en puissance