At the My FlyerTalk level, I see a list of subscribed threads with unread posts. When I click on the indicator (is there a better word?) for one thread, I end up at another. Specifically, when I copy the link while hovering over the indicator, it says www.flyertalk.com/forum/chase-ultimate-rewards/1822133-ultimate-rewards-airline-hotel-transfer-partners-rules-timelines-2017-a-new-post.html. (I stripped out the https:// so that the rest of the URL would not be converted. Is there a better way to accomplish that task?) When I click on it, I see www.flyertalk.com/forum/chase-ultimate-rewards/1462713-ur-united-transfer-not-reliably-instant-4.html#post33321683. If I click on the Last Page link of the thread, it apparently opens the correct thread, but a refresh of My FlyerTalk still shows the thread as containing at least one unread post.

I understand what I'm saying, and I hope it's clear to readers, but I'm not confident. Ask for clarification if needed.

This is a follow-on to my previous post. When I clicked on the unread indicator for thread 1822133 in the Chase forum rather than New Subscribed Threads section of My FlyerTalk, I was again taken to the incorrect thread but it did clear the Unread indicator. Note that the last person to post is shown as KaliFlyer, yesterday at 3:54 pm. However, no post by KaliFlyer is in the thread for that date-time.


thread list entry showing last post by KaliFlyer


actual thread with nothing posted yesterday

Thanks for the report. It won’t be seen by our Tech Support staff until Monday, so in the interim you could try clearing your device’s cache and even cookies if that doesn’t work. (I can’t replicate this error.)

JDiver, Co-Moderator

I can't replicate the error, either. After I followed the (incorrect) link to the first unread message of the thread from the list in the Chase forum (rather than the New Subscribed Threads list from My FlyerTalk), the thread showed no unread messages and so there was no longer any error. But it was odd while it lasted.

Mine sometimes does this but more often it doesn't take me to the first unread post...it takes me to ones that I have already read and I have to scroll down to find my unread post.

This sort of error usually occurs when one thread is merged into another and/or posts are moved from one thread to another. I don't know the mechanics or actual backend details but it seems like the pointer to which thread isn't always updated consistently, which can result in clicking on what you think is going to be the first unread message on some thread but takes you to the original thread of that message before it was merged/moved.

Often the pointer is reset correctly once a new post is added to the end of the thread.

I have been noticing that when on a mobile device, when you go into a thread that has multiple unread post that span multiple "pages", once you have read all the posts right to the end of the thread, when you exit back to the subforum menu of threads, the thread you have just read will show unread items pending.

When you click back into the thread, it takes you to the first posting on the subsequent page in the batch of new posts you have just read, ie. the last read posting is only updates to the end of the first page. You can force the last read post to be reset by clicking on the bottom nav to go to the last page in the thread and then scrolling to the last post before exiting back to the subforum menu.

Anyone else get this?

That's a different problem than what's being reported in the current thread

Some past discussion starting here:

Infinite / Automatic Scroll: issues, q&a, disable on desktop version

​​​​​​Don't count on this ever being fixed. Whatever they may say, from their (lack of) actions on numerous bugs and usability issues, IB could gives zero F's about the mobile skin user experience.

Thanks for the pointer and apologies for hijacking this thread.

That's the tricky part (well, that and actually triggering the issue) about fixing. We actually managed to catch it last week and then, you guessed it, someone posted and fixed it.