Old, read, posts appearing as 'new'

[#1]

@James_B Starting early this morning, posts I have read keep reappearing in the 'unread' list - but randomly - i.e. a post made at 10.00 AM will show as unread, even though I read it around that time, but later posts in the same topic - also read - do not.

[#2]

See screenshot:

[#3]

And again, to prove it is reproducible:

[#4]

Also, probably related, notification of replies to subscribed topics are randomly not appearing in my notification feed.

[#5]

And another 'UNREAD POSTS' feed - including ones I made!!

[#6]

This is an intermittent issue, seen before which I suspect is related to multi-service-instance synch failures.  Or to put it in simple language the right hand does not have a clue about what the left hand did.

These are fundamental considerations with multi -instance services; how does whichever service instance responds to a request know it is dealing with current data?

I suspect similar belies the variable notification count issue, reported elsewhere over 3 months ago, now on “escalation” with the networks team.

[#7]

Fair enough, @Townman , although I don't recall it.

So this is likely to be as long-running and aggravating as the other issue you refer to? 

[#8]

Thanks for reporting this and sharing the screenshots, @jab1 

As @Townman mentioned it's likely related to an open ticket we have with the platform provider so I'll add your examples to it.

James

[#9]

Cheers, @James_B . Also, as mentioned, notifications of replies to subscribed topics are not appearing in my notification feed, randomly - e.g. your reply above.

[#10]

@James_B 

Today I am seeing posts I read on the 24th reported as being new.  Is there any helpful evidence one can gather for you?

To the point, the one I just saw was on the SU board … which 15 or so minutes ago reported zero unread posts.

[#11]

Hi @Townman,

There was some scheduled maintenance completed yesterday so could be related.

Please could you monitor and grab a screenshot if it persists?

Thanks

James 

[#12]

Hi @James_B 

For a starter, my post above just displayed as new, along with yours which is correctly flagged as new.

[#13]

FWIW it now does not show as new … will see if this changes again.

How difficult is it for these folks to look at service multi instance inconsistencies?

One rashly presumes that this service has multi instances over a distributed synchronous database?  If not then the theories of what’s going on are irrelevant, but if correct then the developers ought to be able to run a reference query on each instance and verify that they get the same result.

Either there’s a sync issue or a cache issue.  Someone with knowledge of the architecture ought to have a good clue by now of the circumstances which might lead to this broken behaviour.

[#14]

FWIW, the 'notification' error has not been resolved. Neither has the repeat listing of read posts being relisted as new - for me, anyway.

[#15]

@James_B Whatever Khorus did (or didn't) has had no effect- I am still seeing read posts randomly being shown as unread, and notifications not appearing in my notification feed, eve though the pop-up is still working, rather pointlessly, as there is no way to link the pop-up to a post.