Thanks for the update Cyclops.

Let's see if the daily schedule of new work, at 12:30 UTC, is going to be valid even today. 30 minutes left.
I'll turn on 2 of my computers.....

Edit, added: Yes indeed it worked. I got in total 22 tasks over 2 computers that I started. All assigned between 12:26:58 UTC, and 12:31:56 UTC
1 ARP1, 10 OPN1, 5 MCM1, on one computer, and 3 OPN1, and 3 MCM1 on the other. On both computers it filled up to the project limits I have set. (Two different profiles) Still no OPNG tasks though.

Got 4 OPN units. The log was riddled with transient HTTP errors, but they all finished with no interventions.
Cheers

23 OPN1 tasks today, in between 12:26:07 UTC, and 12:36:09 UTC. I'm using a batch file with auto-request every 5 minutes, so I do not have to babysit my computers.

Yeah, I have noticed the same. When you get a resend, it's usually outside of the 12:30 UTC window, when they dump the daily test batch. So anything going out at other times, doesn't have any download problems. So the "transient HTTP errors" , is clearly a network capacity problem. At this point, it would be much better if they spread out the delivery of the test batches over the full 24 hours day, instead of dumping it in one go. In that way, they could slowly ramp up and find out how many tasks they can send out per hour before the transient HTTP errors show up, and work from there with the data center.

One would think the IBM team provided, "Here's our existing pipe and throughput usage stats, here's our storage pool stats, here's our compute numbers, so you'll want to at least have the same or more."

Honestly I do remember a lot of the IBM infrastructure actually used IBM hardware and software so I'm not sure if that's carried over or if there's been a migration to other stacks.