# Timeline navigation misbehaving starting from 10000 posts

**URL:** https://meta.discourse.org/t/timeline-navigation-misbehaving-starting-from-10000-posts/164100
**Category:** Support
**Created:** [September 15, 2020, 3:40pm UTC](https://meta.discourse.org/t/timeline-navigation-misbehaving-starting-from-10000-posts/164100 "2020-09-15T15:40:46Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Canapin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/canapin/32/119591_2.png) [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [September 15, 2020, 3:40pm UTC](https://meta.discourse.org/t/timeline-navigation-misbehaving-starting-from-10000-posts/164100/1 "2020-09-15T15:40:46Z")

</div>

Hi.  
I noticed after an import that the timeline navigation don’t work properly on 10000+ posts topics.  
If you drag’n drop the cursor on the timeline, it will scroll to the post, but won’t update the timeline cursor until you scroll again manually:

My max reply limits is the default one: 10000. So it shouldn’t be an issue…  
Except that Discourse closes a message at the post number 10000, and add another reply (automatic closure), which makes 10001 posts.

But even at 10000 replies, the issue occurs.  
However, the issue disappears as soon as delete posts to have 9999 replies (including the automatic closure message):

So, the issue occurs naturally when the topic reaches 10000 replies, and not only for existing megatopics.

I increased the **auto close topics post count** setting but it didn’t resolve the issue.  
I also tried to change the short progress text threshold and it didn’t help either. Weirdly, even by increasing this setting to 15000, the timeline cursor doesn’t show the date on a 10000 posts thread 🤔

 ![image](https://global.discourse-cdn.com/meta/original/3X/0/4/0400bbfe9eba8fc54b74ffdee91048d296da7148.png)  
But that may be another issue.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [September 15, 2020, 4:53pm UTC](https://meta.discourse.org/t/timeline-navigation-misbehaving-starting-from-10000-posts/164100/2 "2020-09-15T16:53:00Z")

</div>

> [@Canapin](#):
>
> If you drag’n drop the cursor on the timeline, it will scroll to the post, but won’t update the timeline cursor until you scroll again manually:

This is because

> [@Performance improvements on long topics?](https://meta.discourse.org/t/performance-improvements-on-long-topics/30187/27):
>
> Jumping to an index on the timeline becomes jumping to the closest post number on the timeline

> [@Canapin](#):
>
> Weirdly, even by increasing this setting to 15000, the timeline cursor doesn’t show the date on a 10000 posts thread

We remove a lot of features on mega topics to preserve performance. Our general recommendation is [The MEGATOPIC: public good, or public menace?](https://meta.discourse.org/t/the-megatopic-public-good-or-public-menace/85592)

> [@Topics over 10,000 posts remove "Frequent Posters"](https://meta.discourse.org/t/topics-over-10-000-posts-remove-frequent-posters/107671/4):
>
> Yes, server load gets exponentially higher with large topics. We put in some basic mitigations (you’ll note that dates don’t appear on the timeline, etc) but it’s still expensive.

> [@Topics over 10,000 posts remove "Frequent Posters"](https://meta.discourse.org/t/topics-over-10-000-posts-remove-frequent-posters/107671/6):
>
> The number of megatopics in the wild is minuscule, investing large amount of time optimising this means we have less time working on features which are much more commonly needed.

---

<div class="post-metadata">

### Author: ![Canapin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/canapin/32/119591_2.png) [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [September 15, 2020, 5:25pm UTC](https://meta.discourse.org/t/timeline-navigation-misbehaving-starting-from-10000-posts/164100/3 "2020-09-15T17:25:12Z")

</div>

Thank you for your reply 🙂  
I’ve read these post and I understand why megatopics are wrong.

The main “problem” to me is just that the issue course naturally with default Discourse settings, and wouldn’t occur if the limit was 9998 instead of 10000. But I acknowledge that this is a rare issue and a very minor inconvenience. 👍
