Dacker - I have been with Rosie since the early days, so I have watched its decline.

What is going on is that they release small batches of work from specific proteins that the Robetta AI spit out that they want to look at further. They then study them further and when they are done they drop another load. You don't get much work because the number of computers exceeds the amount of work that is put out.

I left this year and occasionally check back, but I see nothing has changed.
Its still sporadic, lots of people sign up, maybe some leave their systems attached, i don't know. But the days of raw protein searching are gone.

There will be no communication from anyone on the team. You and the rest of the volunteers are left on your own to figure out any problems.

If you want to do protein folding still, non BOINC then download and Folding at Home. They have cpu and gpu work all the time. They never run out. It's just not BOINC.

That was a known issue because the servers were not back online yet.
The way the comments have been going, you can upload work, but not download new work just yet.

Go here to watch the tech talk news about their progress. Its updated once a week or sometimes more often. Just depends.

Current status:
10/9/2025 7:03:42 PM | World Community Grid | Giving up on download of scc1_06_v01.png: permanent HTTP error
10/9/2025 7:03:42 PM | World Community Grid | Giving up on download of stat_v05.png: permanent HTTP error

I had V 7.2.47 on my computer for a long time and got HTTP errors and nothing uploaded since BOINC went down a month ago.

Just updated to 7.16.11 and all the uploads went up.

Unfortunately it looks like there are no tasks on any projects running so more waiting.

In regards to WCG...don't do a damn thing with your pc.
Restarting will not clear the problem. New BOINC will not solve your problem either.
You can upload apparently, but downloads are http permanent failures a few hours ago. The servers are not working right still as of a few days ago. They are working on things at the project level now. System level seems stable.

You guys need to read your BOINC logs and if you get http errors or something else, its not your pc or BOINC. Its all WCG.

October 7, 2025

We have resolved the issue with the BOINC scheduler configuration causing "Another scheduler instance is running for this host". Users should be able to report tasks. We will update as soon as we begin creating new workunits as we are still working to stand up the rest of the BOINC backend architecture.
Website went down briefly as we brought the scheduler online. We have adjusted the HAProxy configuration, and we will continue to adjust Apache/HAProxy config if we see the website stops responding again.
Still debugging issues with the new Kafka-based validation workflow that works together with HAProxy routing rules to partition BOINC downloads and uploads by assigning servers equal hex buckets using the https://github.com/BOINC/boinc/wiki/DirHierarchy BOINC expects, and emitting events from the new file_upload_handler we wrote to Kafka so we can batch and respond to them in parallel. This removes the need for multiple round trips to the database for row-wise operations and polling, which are now simply batch applications of state after consuming workunits ready for validation in the relevant Kafka topic for that application. This allows us to perform validation and assimilation in the same process, at least for the projects we run ourselves (MCM1, MAM1, ARP1), and while the Kafka/Redpanda learning curve was significant, we have successfully transitioned to an event-driven in-memory partitioned architecture that should let us keep pace with the upcoming GPU enabled MAM1 application.


If you don't understand this, then a chatbot will help bring it to a level you can understand better.

All of my completed workunits vanished and the logfile says they aborted upload. Oh well, at least it was only about 2-3 day's worth of work.