Users are reporting a recurring issue in Discourse 2.9.0.beta9 and 3.3.0.beta1 where the message “Sorry, we couldn’t load that topic” appears during various interactions, such as clicking avatars or viewing likes. piffy notes the problem occurs randomly on desktop and suspects a recent update or plugin issue. Don suggests the error may occur when a topic is deleted after being shared, leading to broken links, and recommends checking logs for related errors. piffy confirms most log errors are tied to a custom Discord plugin and plans to debug it. Gunnar also reports similar complaints post-rebuild but finds no relevant logs, indicating the issue may be widespread and possibly tied to plugin conflicts or edge cases in topic deletion.
Sorry, we couldn't load that topic, possibly due to a connection problem. Please try again. If the problem persists, let us know.
My site is a few months old, it could be coincidence that two people decided to report this issue on the same day. But it could also be due to a recent commit.
I think this is happens when the topic and the topic author is deleted but the topic link is shared and still available on an other topic so that is still exist and clickable. When you click it this page comes. I believe there should be some errors related with this in /logs.
Edit: Now I cannot reproduce it but It happened once on our forum. A new userA create a topic, userB share that topic in other topic. Than userA is delete himself so the previously created topic is also deleted. After this when click the link what userB shared get this error page. But maybe it caused by a plugin for us
My users are reporting that it happens with basically random interactions on the site (desktop only).
Quote:
Similar things happen to multiple functions. Clicking the top right avatar, pressing the number left to the heart to see who liked something, leaving likes (this is rare), viewing the leaderboard.
Thanks for the tip about the /logs page, I forgot that exists. I have a custom discord plugin I’m running and it seems most of the errors on the page are related to that. I will attempt to debug it soon, if the problem in the OP exists after that I’ll bump this topic. Thanks again