I’m still doing experiments to try and pin down the exact cause, but I’ve ended up with a history where I can’t download at least some dataset collections. Some of this is stored on Backblaze B2 and connected as Bring Your Own Storage, some of it not (but copied from the same BYOS):
I am going to do some more experiments, but for either of these (TB-Profiler JSON output) the result for attempting to download the collection is a 503 error.
My next experiment is going to be to re-run the analysis workflow start-to-finish on .eu storage and see if the problem persists.
I ran a smaller set of data through the same analysis workflow, history ID 136925a1d66d947a , and was able to download without problems. So I think this definitely seems to be a BYOS problem.
The problem is now solved. We have applied new fixes and deployed them. Additionally, I have tested both the shared links and can confirm that they are now downloadable. However, since these are rather large collections, it takes a little longer to download.