# New / Unread counts missing when "too many tracked topics"

**URL:** https://meta.discourse.org/t/new-unread-counts-missing-when-too-many-tracked-topics/32922
**Category:** Feature
**Created:** [4 سبتمبر 2015، 6:37م UTC](https://meta.discourse.org/t/new-unread-counts-missing-when-too-many-tracked-topics/32922 "2015-09-04T18:37:23Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [7 سبتمبر 2015، 2:06ص UTC](https://meta.discourse.org/t/new-unread-counts-missing-when-too-many-tracked-topics/32922/8 "2015-09-07T02:06:44Z")

</div>

I think I am ready to put this to rest post this commit: [FEATURE: implement capping of new/unread · discourse/discourse@335be27 · GitHub](https://github.com/discourse/discourse/commit/335be272ffac925fe84970f460e2d933d8d98832)

Copied from commit message:

We cap new and unread at 2/5th of `SiteSetting.max_tracked_new_unread`

This dynamic capping is applied under 2 conditions:

1. New capping is applied once every 15 minutes in the periodical job, this effectively ensures that usually even super active sites are capped at 200 new items (+ number of new topics created in 15 minutes)

2. Unread capping is applied if a user hits max\_tracked\_new\_unread,  
meaning if new + unread == 500, we defer a job that runs within 15 minutes that will cap user at 200 unread

This logic ensures that at worst case a user gets “bad” numbers for 15 minutes and then the system goes ahead and fixes itself up

This resolves the issue completely even for super active sites like @charleswalter heloforos, with ZERO config needed by users or admins, and no confusing message to end users.

---

_[View the full topic](https://meta.discourse.org/t/new-unread-counts-missing-when-too-many-tracked-topics/32922)._