yafu-low used to send 1 or 2 units down, now it gives the job cache full error.

Since it will never send down more than 2, and it is often empty server side, another project will always fill up the cache and no more YAFU. smalls.

Both projects are set to 49 resource share and a 3 day cache with 0 additional.

I don't want to be manually pausing one project then requesting YAFU-LOW every 2 hours.

Yes, the project is configured in a way that you will have only 2 workunits on your host.
There are reasons for it.
Sometimes I change it to 3.

Yes, the project is configured in a way that you will have only 2 workunits on your host.
There are reasons for it.
Sometimes I change it to 3.

Yes, yes, yes, I've been working on the project for 3 years now and this is not news.

Last month yafu small sent down WU even if the cache was full.
Now it refuses.

Have to pause other high priority project manually and sit and request yafu-small manually 10- 20 times (per 32 computers, 300+ mouse clicks and an hour of my time) to get 2 tasks per machine that might be done in 3 minutes or 3 hours.

Something has changed.

I want to get 100,000 WUProps hours in on yafu-small but can't allow it to have all the cores as it's too unreliable to obtain, doesn't pay well and it's central thread is set to normal priority (not idle) so it dominates the cores and won't share cycles.