That's interesting, if one looks at a webservice request for this release, one can see that the result does not contain any relationship for recording or works:
The same request for another, much simpler release, does:
I think there was some server side change that prevents loading the relationships for such a massive release. Can somebody confirm that?
But actually without that change I would have expected the server to fail. We had this come up a couple of times, where the server failed to load a large release with too many relationships and just returned an error. If you got this issue in Picard the only workaround was to disable track relationships (or even release relationships).