Sorry, we couldn't load that topic

We’ve had a spat of complaints about this issue now, after the latest rebuild of our site to 3.3.0.beta1 (ba04fc6a01).

I’ve looked in the logs, but couldn’t find anything related to this.