# Solved count in summary displaying incorrect values **URL:** https://meta.discourse.org/t/solved-count-in-summary-displaying-incorrect-values/359134 **Category:** Bug **Tags:** solved **Created:** [March 27, 2025, 11:18am UTC](https://meta.discourse.org/t/solved-count-in-summary-displaying-incorrect-values/359134 "2025-03-27T11:18:13Z") **Posts on this page:** 1 **Showing post:** 1
### Author: ![dr460nf1r3](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dr460nf1r3/32/484691_2.png) [@dr460nf1r3](https://meta.discourse.org/u/dr460nf1r3) #### Post date: [March 27, 2025, 11:18am UTC](https://meta.discourse.org/t/solved-count-in-summary-displaying-incorrect-values/359134/1 "2025-03-27T11:18:13Z")
Hey everyone, After updating our Discourse instance, we seemingly have incorrect solved amounts when looking at profile summaries. Example: - Wrong: [Profile - dr460nf1r3 - Garuda Linux Forum](https://forum.garudalinux.org/u/dr460nf1r3/summary) - Correct (from profile popup): ![This image shows a screenshot displaying a user profile from a social media platform, indicating the user has recently posted, joined the platform on April 27, 2020, and read 40 posts and 485 solutions, with a prompt to view 475 more posts in the "D" section. (Captioned by AI)](https://global.discourse-cdn.com/meta/original/4X/6/0/c/60ccb8f8525f129f167764b19ddcb5fa71dafbf9.png) I already noticed there were a couple of changes lately, including a breaking bug: > [@Solved topic cannot be loaded](https://meta.discourse.org/t/solved-topic-cannot-be-loaded/358947/7): > > 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 The correct amounts are obviously still available so there was likely something happening while migrating the data to the new tables? --- _[View the full topic](https://meta.discourse.org/t/solved-count-in-summary-displaying-incorrect-values/359134)._