# Solved topic cannot be loaded

**URL:** https://meta.discourse.org/t/solved-topic-cannot-be-loaded/358947
**Category:** Bug
**Tags:** solved
**Created:** [March 26, 2025, 1:33pm UTC](https://meta.discourse.org/t/solved-topic-cannot-be-loaded/358947 "2025-03-26T13:33:34Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![nat](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nat/32/235063_2.png) [@nat](https://meta.discourse.org/u/nat)
#### Post date: [March 26, 2025, 5:55pm UTC](https://meta.discourse.org/t/solved-topic-cannot-be-loaded/358947/7 "2025-03-26T17:55:54Z")

</div>

This has been fixed here: [FIX: Some solved topics have no answers by nattsw · Pull Request #350 · discourse/discourse-solved · GitHub](https://github.com/discourse/discourse-solved/pull/350)

Extra note:

When using custom fields, there are very little validations available so marked answers may be dangling, leading to posts that do not exist, or topics pointing to the same post.

We _just_ moved discourse-solved away from using custom fields into proper tables, and there had been some assumptions made like each post should only be an answer to a topic, or a topic with an answer must point to a non-null post. All these assumptions were thrown out of the window

 ![yeet](https://global.discourse-cdn.com/meta/original/4X/c/e/2/ce2995c602ccaa3f6f88cb3473e0f600d34a7111.jpeg)

---

_[View the full topic](https://meta.discourse.org/t/solved-topic-cannot-be-loaded/358947)._