Took a break from Seti@home for a few months. Just started BOINC back up again and I can only get one workunit in the cache. I have increased store at least under computing preferences to the values I used to use for a full cache but I still get just one wu in the cache.

I suspect I changed a config parameter somewhere before I took the break, but now I cannot find anything obvious that I may have changed.

It can take some time for your cache to build up.
It is worth knowing that these days SETI has a task count limit of 100 for your CPU and 100 per GPU. To make sure you sit near these limits set "Store at least" to about 3 to 5 days, and "Store up to an additional" to a very small number - I use 0.01 days. Setting the "additional days" to a large value can cause problems with large delays in fetching work resulting in violent swings in numbers of tasks in your cache.Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Perhaps it is the settings in the View (Home,Work,etc) that you need to check. Since your computers are hidden (please Unhide them) we can not see what tasks you are running. I know this happened to me when I had checked Home, and the WU was set to Work.
SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Post your first 30 lines of the Event Log after first startup. Also post the contents of cc_config. That is where the restriction likely resides.Seti@Home classic workunits:20,676 CPU time:74,226 hours

Under SETI preferences, do you have the Resource Share set to 0? In the past, this was done to limit BOINC to getting 1 WU at a time (for backup projects) so when SETI came back up from an outage, it would take over the machine again with no stored work for the backup to run through.

I had this issue few days ago realized didn't realize there was a BOINC Manager Comp Prefs as well as the seti@home pref settings, I was getting 5 or 6 GPU/CPU..
I have mine at 10 days of work ( prolly to much)
and store up to an additional 0.01days of work now get 100 of each..

If you are getting 100 tasks per cpu and 100 tasks per gpu, then the 10 days of work cache setting is meaningless. The project has a hard limit of 100 tasks per cpu/gpu at any time. You could probably drop the initial work cache setting down to 2 or 4 days and you would still only get 100 tasks per device. That also depends on the device APR.

The 'store additional days of work' setting at 0.01 days forces the Client to contact the project often to keep topping up the cache tank so will always be at 100 tasks per device. The 10 days of work cache setting is a archaic reminder of the early days of the project with slow cpus and intermittent Internet connections.Seti@Home classic workunits:20,676 CPU time:74,226 hours

I know you have slow devices, but considering the current SETI task deadline is two months out from issue date, I don' think you will ever run into not being able to finish a task before deadline.

MilkyWay takes care of cache by limiting maximum allowed tasks at any time to 80 tasks. Einstein is where you could run into troubles as it always issues too much work. But if you have it as only a backup project to SETI with resource share of 0, it shouldn't overwhelm your system when SETI has troubles.

I would probably drop your initial cache down to 2 days and see how that works out. Again, I think the scheduler will keep your cache at 100/100 irregardless of how many days of cache you have set.Seti@Home classic workunits:20,676 CPU time:74,226 hours

Everything looks correct on your system with the Optimized apps. It correctly configured the SoG app for the very slow gpu as a low performance device so it shouldn't impact the system responsiveness.Seti@Home classic workunits:20,676 CPU time:74,226 hours

If the host has an average of return of close to 4 days, why it's send 100+100 WU if the cache is set for 2 days?

I know on this case the times will drop after the configuration but the server did not know that for now until it start to receive the crunched WU. So why send too many WU to a slow host and why it not respect the 2 days cache?

His host has a actual APR and turnaround time of about 1 1/2 days. The BOINC main host stats page only updates every 24 hours. The Applications Details page updates every couple of hours. It will take a couple of days for the main page to reflect somewhat accurate values. And yes, the scheduler is mostly broken as we well know.Seti@Home classic workunits:20,676 CPU time:74,226 hours

I think my initial problem was that I had not crunched for a few months and the scheduler was only giving me one at a time until I had enough work units validated. I seem to get plenty of WUs now.

But, I have another problem. I would like to switch to just Astropulse only. I used to do that on the SETI@home preferences web page and set AstroPulse v7: yes, SETI@home v8: no. I have done this today for all the different groups but I still get Seti@home work units. Does this setting still work?