Read stories aren't staying read.

Like just about everyone here, I check my RSS feeds every few hours. For the past few days, I’ve been noticing that a handful of the stories I read during a previous news-reading session have been marked as unread again. It’s difficult to replicate this bug, meaning it doesn’t happen every time, but it’s been happening enough times that I wanted to bring it up here.

This isn’t the end of the world. I don’t mind tapping the “J” key a few more times on my keyboard. But it didn’t used to be this way. :smiley: :smiley:


Are the stories consistently from a few popular feeds? Are they shared by anybody? Do you mark the feeds as read ever? 

I haven’t made any changes, but I am about to launch an enormous change to how feed’s get fetched to fix those SNI issues that have been all the rage this past month. So I’d like to figure out what’s going on. The original issue of read stories not staying read has to do with shared stories.

Are the feeds that this happens to feeds that publish many, many stories in a month? It’s possible the stories are being trimmed but are still in the RSS feed. Are these the oldest stories that NewsBlur has for the feed (browse by Newest First and scroll to the very end).

It happened again this morning.

To answer your questions:

Yes, this is happening to news items from popular feeds (big tech sites).

I’m not sure if they’re shared by anyone since I turn all the NewsBlur social features off (sorry).

And I mark everything as read. I basically just open NewsBlur and start furiously tapping the “J” key.

Bump. This is still happening to me. It was OK for a few months, but these past few days have been brutal.

Hmm, nothing has changed on the backend and service is normal. Which feeds is this happening to? And is it a block of stories all at once? Are the stories from way back or something you just read?

Something I just read. Mainly The Verge and Techmeme.

Edit: Just happened again with those sites above, plus Android Police and Mediagazer.

I’ve noticed this will sometimes happen when I have a flaky connection on iOS. I will read through a feed, and some of the items will appear as unread once the connection is re-established. It happens infrequently enough that I would guess it is a race condition where the right thing happens 99% of the time.

It sounds like this is happening via the web, though. It may help narrow down the problem if you can open the browser console next time it happens, and copy the previous minute’s worth of logs.

Yeah, if you can share the error code on the /reader/mark_story_hashes_as_read endpoint (like a 500 error or 502 or 503) that would greatly help! Just open up the dev console when it happens and LMK if you see an error (and take a screenshot!).

I have some logic in place to handle that, but it may be faulty, since it’s an exceptional case and hard to debug.

uhhhh i have no idea how to do that :slight_smile:

also, i’m not on a flakey connection. home wifi. 80 mbit connection.