Thanks for the history on the cam25's. I found the one in question, and it has returned 18 zips.
https://www.cpdn.org/cpdnboinc/result.php?resultid=21709022

However, the ones that are stuck are #12 and #13. So it looks like they got lost in the shuffle.
If they have not uploaded by the time my other work has finished tomorrow, I will just can them
(as in trash can; I just realized that may not be clear to non-native English speakers).

What I've done with previous CAM25s that have persistently stuck uploads is just abort the transfers that are obviously stuck. After aborting the transfers, it will report the task, possibly as a success, and the scientists can determine whether the output is useful without the missing zips. I've only done this with the CAM25 tasks however since those are the ones that seem to occasionally have the rogue stuck uploads.

CPDN has a track record of computation errors when suspending tasks so I sure ignored that part. I don't blame any one else for it either.

I left the 2 that had not started yet suspended but the ones that had started I let them complete even if the uploads will take awhile.

Never seen a problem from suspending tasks if BOINC isn't stopped and restarted. Also a long time since even doing that I have lost a Windows task.

Just to reiterate so the information stays near the top of the thread, Clearing the data and the backlog of people still uploading data some of whom have several hundred gigabytes means that it could easily be a week or more before the problems stop completely. Also no need to suspend any tasks other than sam50's as they go to different servers.

All of my Linux zips on three machines have gone, so that is progress. But I have over 50 WAH2 zips on my windows machine still stuck. It seems to be discrimination against North America.

A week or two someone also reported that Free-DC cannot get new stats from CPDN and the issue is on CPDN site. So issues ;)

There is now a batch of 28 month pnw25 tasks out there. Batch 757

Some of these are already on their third attempt with a combination of download errors and being aborted. I suspect this is the download server being out of action referred to elsewhere.

Yes, the march / April stuff may be a problem, as there was no "real" server to return data to around about that time.

Which is why I kept posting that people shouldn't try and get new work, or return old results.

Still, I don't think that recovery is over yet.

Now awaiting the clamour from those who think they should have more.

or if we got credits it wouldn't really be that big a deal...

Once things are fully sorted, credit will be granted again. There was an attempt to run the credit script last week but it didn't complete. Andy has started to go through the logs looking for the problem. I think he said it got to about the 7 hour point before it failed.

I don’t know how many credits you think thqt you lost get over it. I lost about 1.3 million.