Very recently on MilkyWay@home, I deprecated the latest version of milkyway_nbody (v1.80) and un-deprecated an older version (v1.76) to run some optimizations using the older version. However, since the current workunits from my last set optimizations were incompatible with the older version, and because I didn't want to scare all of our volunteers with computation errors, I cancelled all of the old workunits (roughly over 200,000) before the deprecation using the Cancel Jobs by SQL option in milkyway_ops. I then put up 3 new runs using the older version of milkyway_nbody.

After about a day, I discovered that BOINC had not sent out any of the new workunits. I can see that 999 jobs were created for one of the three optimizations (none for any of the others), but no workunits are being sent out at all.

Does anyone have any insight as to what is happening?

Probably best asked at MilkyWay@home.

I think he is Milkyway@Home, as to me it sounds like he's talking about deprecating work, not canceling tasks in his cache.

@AxiomOmen, I think you best ask at the BOINC Projects email list https://groups.google.com/a/ssl.berkeley.edu/g/boinc_projects to get help from fellow project admins, and/or the developers. We're mostly helping people with their client problems these days.

In that case, my apologies.

I figured out what the problem was. We had an issue with the signature files changing between versions last update. Since the older version was using invalid signature files, MW@home was not sending any executables. We rereleased the old version as a new one with updated signature files, and now I'm receiving nbody workunits.

Thank you all for your time looking into this.