It is NOT DDDT2 only.
I have been running DSFL for weeks now.
(Still checked !)

DSFL IS still selected.
Has been for weeks.
Have not changed anything.

(Have now added SN2S for now.)

Edit: "Opposed to your log, mine does print there's no DSFL:"
Maybe because I'm still running 6.10.58 ?

I sure hope it's just temporary. I'm only less than 2 weeks away from my Sapphire badge

Talking to techs last week, they are aware of the confusing / incomplete messages v. work requesting and assigning. Right now it often requires an analyst to interpret what it's saying... tomast log a good example. Similar GPU / CPU work messages need updating.

That said, it's not only the server messages, as also the client messages on GPU/CPU have needed work. Latest 7 client has some improvements on that. (Now testing 7.0.27... several have asked for 7.0.25 retraction as that was a hip shooter. 7.0.27 is the first one that seems to install proper in W8-consumer preview when not choosing the server / protect appex option, and that is needed [still] if wanting to do GPU crunching on Widdows )

All that said, the *select* posting that members at times do, leaving out anything informative that is logged before and after the lines that alert a user does not make for easy assistance.

Whilst, since no one else jumped on the "Cant have DSFL", either they had the fall-back option (of course recommended), or enough cache to bridge the temp shortage, or it was just that the feeder was clogged with other work, or the day share was used. There are only so many ad hoc slots in the shared memory area. And, from stats note that the Thursday/Friday mean run times jumped from 5 to 6 hours and still as many were validated as on workday Wednesday... 89K compared to 70K on last week Saturday.

--//--

edit: Oops, last Saturday was perturbed due the server hosting networking upgrade.