Ambiguous notifications count

[#1]

Good news, @Townman - Khoros have been able to observe the problem and have identified a server-side caching issue. It'll be cleared during tonight's maintenance window so please let me know how things look tomorrow.

James

[#2]

@James_B 

A big THANK YOU for being stubborn!!

That is exactly the character of what I thought (up to a point) might be the issue.  I've seen this previously, but never had solid evidence of it and have suspected inconsistent data between service instances.

My expectation here is that the count will be consistent after this fix, though capped at 101.  It would be interesting to know what is my current notification count before I take action (look at the page) which will clear the counter.

[#3]

No problem, @Townman 

I've asked the question about your current count.

James

[#4]

Good morning @James_B 

Today’s experience is unchanged from yesterday, counts of 101 followed by (currently) 65 are still being reported.  Was the change implemented?

There has been a slight change in the observed behaviour - sometimes after making a post, 101 is reported rather than the lower count.

[#5]

Thanks @Townman 

I believe so but I've emailed Khoros to check it was done and ask if any action is required at your end.

James

[#6]

@James_B 

As another POETS day comes to a close, the experience remains unchanged, all hope that they might have cured it appears to have been dashed.

[#7]

@Townman - Khoros have escalated it to their infrastructure team. I'll keep you updated.

James

[#8]

Good morning @James_B 

Another POETS’ day has arrived.  Is there an update please?  Do they understand anything around the issue?  Have they advised on my notification counts by type or confirmed a scenario leading to a 101 ceiling.  Have they identified a session timing or status event which causes the count to change?

Have they concluded that there might be more than one issue here?

[#9]

Nothing since Tuesday's update I'm afraid. I'm meeting with Khoros today so I'll escalate.

James

[#10]

@James_B 

Another week has passed, indeed another month has passed.

Are they actually doing anything, or are they hoping I'll just give up pestering?

This has now been around nigh on 3 months.

[#11]

Hi @Townman,

I've had no new updates since it was passed to the infrastructure team. I'll chase now.

Thanks

James

[#12]

Hi James,

Any news?  Is this likely to be resolved in the next maintenance cycle mentioned elsewhere please?

[#13]

Unfortunately not, @Townman - this one is still with the infrastructure team.

James

[#14]

@James_B 

5+ weeks with the infrastructure team ... and no updates offered.  Really does suggest that these folks really care about the user experience ... not!

I have some reason to suspect that the notification algorithm has been changed.  101 remains the cap, but the lower figure has fallen to 30 ish which given I've been around here far less than usual I would not expect the notification counts to be falling.  I have deliberately not touched the notifications page since later 2025 to keep the evidence in place.  Similarly I have hardly touched the email space as there is limited help one can give in the face of the many challenges.  I have 2300+ unread posts therein, so I find it off that the 'background' notification count should have decreased by 40%.

[#15]

I'm just as frustrated as you, @Townman 

I'll continue to escalate and let you know as soon as I get an acceptable update.

James