Twice now, projects that were configured 'No New Tasks' have reverted to their previous status / mode, i.e., soliciting work, downloading work, processing WU, upload results, petitioning for - and obtaining - credit.

I want to say that it even came out of Suspended, but I can't; I don't remember what I did. In both cases - Rosetta and Einstein - I had previously bitched on their respective support forums about they throwing me to the curbside; support for my hardware platform / OS was no longer supported.

Dunno. But I will state that both times this occurred, WU started crunching again - despite NNW or SUSPENDED status / config - and they not only complete, I gets credits too!

Dunno, but this SSE constrained BOINC project participant thanx u; heart heart heart penguin.

There are some things that override Suspend Network, like you pressing the Update button. But as far as I know there is nothing, aside from a human, that can get a project off NNT.

I have most all of my projects on NNT all year round, and this BOINC (7.6.22) is attached to a lot of them (50+). So I don't know what to tell you, other than ask potential family members, or the cat, if they pressed keys?

One other possibility is that you put an older backup of the client_state.xml file back, or of the data directory, where the previous status was not suspended/NNT. I'm just thinking, not saying you have done any of that.

When a project gets taken from NNT, it will show in the Event Log. Like so:
14/02/2016 02:24:24 | Pirates@Home | work fetch resumed by user

So the only option I can give you is to set in cc_config.xml options that the stdoutdae.txt file is a portion larger than the default 2 megabytes and when you next notice that a project previously on NNT is fetching work again, that you go search through the log what happened.

<max_stdout_file_size>20119200</max_stdout_file_size>

The above sets the stdoutdae.txt file to 18MB.

---

Are you using an account manager?

---

My Detailed BOINC Stats