Post_created data not matching actual posts

AI-generated summary

The discussion focuses on a discrepancy between user post counts in the Discourse API and actual posts. Theo_Deliivanov reports that for a specific user, the /u/X/summary.json endpoint and admin list show only 3 topics and 2 replies (totaling 5), while the admin panel displays approximately 9 topics and 10 replies (totaling ~19). The missing posts date from August to mid-October, suggesting counters may have been reset or rebuilt around October 21–22.

Theo asks for potential causes, such as accidental restores or upgrades, methods to recalculate stats for all users, and reliable ways to track total post counts. NateDhaliwal inquires if the posts are in PMs or gated topics, but Theo confirms they are not.

Hey,

I’m seeing something odd with the data returned for our accounts lately and hoping one of you can shed light on it.

The endpoint stats say user X has 3 topics and 2 replies (that’s what /u/X/summary.json and the admin user list return). But the profile shows way more. By my count in the Admin panel it’s 9 topics and about 10 real replies, once I leave out the pinned/unpinned entries. So roughly 19 posts versus 5 in the stats.

The odd part is that the numbers that are counted look like only the latest activity. The 3 topics are the ones from Oct 22, and the 2 replies are the two newest. Everything from August through mid-October isn’t counted at all, or at least no other topics are reflected. It looks to me like the counters maybe got reset or rebuilt around Oct 21–22, but I can’t see why that would be the case.

Could you help me with a few things?

  • What might be the reason for that?

  • Can we see if anything happen to the sandbox around then? A restore, an upgrade etc? Can that be triggered accidentally with any of the settings?

  • Can we recalculate the stats for all users?

  • What would be the most reliable way to keep track of total post count + replies?

    Thanks!

Are these topics and replies in PMs or gated topics (e.g. #staff)?

Neither of those is the case for us