Ambiguous notifications count

[#1]

@James_B 

As of this afternoon, I am seeing the same symptoms again - either 50 something or 70 something.

I was aware of it being 53 ish ... and then saw it report as 73 ish and though someone has been busy hitting my recent posts.  Having made another post, it is back down to 50 something.

The profile is back, but I have yet to hit the counter ceiling.  Can a proper investigation please now be conducted by the vendor.  I suggest that they start by finding the counts of different types of notifications on the account please.

[#2]

After a pause...

Pre-posting and during posting.

[#3]

Immediately after posting...

Time as per this and previous post timestamps.

[#4]

@James_B 

Are you able to advise if this update has been passed on to the vendor please?

[#5]

Hi @Townman,

Yes, I've passed that over.

Thanks

James

[#6]

@James_B 

Grizzle, grizzle and more grizzle!  Looks like someone zeroed my reminder count again!

[#7]

Oh dear, @Townman, I haven't been notified of any action taken that would cause that.

I'll update the ticket to let them know (in case it wasn't intentional). Moving forward, please continue to use the notification feature as you normally would and drop me a message with any further odd behaviour (with timestamps if possible).

Thanks

James

[#8]

@James_B 

Odd!  The counts have returned!!!

I will reply to the PM when back home.

[#9]

Hi @James_B 

Sorry for the tardy response ... been "frying other fish".  Oh the joys (!) of SVG mark-up!

Responding to the PM points ... there's nothing private, so answers might inform others.

• Count dropping to zero: there was nothing specific beyond making 'normal use' of the service - I cannot recall if the count suddenly became zero following doing something or I returned to a session to find the count apparently reset, the only residual count referred to PMs
• Count remaining zero: Thinking this could be a session issue matter, I logged out, logged back in and the count remained zero - I grizzled, reported and got on with accepting the count history / evidence was lost
• Count restored: out of the blue, a sizable count number was again reported - somewhat happier but doubly bemused
• Indicators: There was NOTHING to suggest an exception event
• Console logs: Not something inspected as a matter of course, but if there is something the vendor was to explore, some guidance on what to look for and when would be useful
• Issue has been seen with Edge on Win10 and Win11 and Safari in iOS26 and probably in Silk on Amazon Fire

I do not see this as being a client side issue BEYOND which server instance the client is currently connected to.  Is there any tell-tale information on the console log which might help determine such?

has anyone looked at the notification counts by type on my account?  Notifications are...

• Replies
• Thanks
• Mentions
• PMs

The last is clear, distinct and does not appear to have issues.

The rest appear to have a capped reporting figure of 101.

In some circumstances one or more of the three are omitted in some reported counts.

As I write this post, the counts are 93 + 2

[#10]

On completion of the above post 50 "disappeared"!!

[#11]

Are these console message of any relevance?

Access to XMLHttpRequest at 'https://api.iterable.com/api/inApp/web/getMessages?count=1&packageName=donation-reminder&platform=We...' from origin 'https://community.plus.net' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

retailer.js:2 Error fetching messages from Iterable X {message: 'Network Error', name: 'AxiosError', code: 'ERR_NETWORK', config: {…}, request: XMLHttpRequest, …}code: "ERR_NETWORK"config: {transitional: {…}, adapter: Array(3), transformRequest: Array(1), transformResponse: Array(1), timeout: 0, …}adapter: (3) ['xhr', 'http', 'fetch']allowAbsoluteUrls: truebaseURL: "https://api.iterable.com/api"data: undefinedenv: {FormData: ƒ, Blob: ƒ}headers: St {Accept: 'application/json, text/plain, */*', Content-Type: undefined, Api-Key: '1da04c82a5e34d97903d2ce7b68bb3f3', Authorization: 'Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2…yNzJ9.ldrr4gWwQGlUERcPRIO-niPY8vBx-pCl4IhDDqQINn8'}maxBodyLength: -1maxContentLength: -1method: "get"params: {count: 1, packageName: 'donation-reminder', platform: 'Web', SDKVersion: '1.2.0', latestCachedMessageId: undefined, …}paramsSerializer: {serialize: ƒ}timeout: 0transformRequest: [ƒ]transformResponse: [ƒ]transitional: {silentJSONParsing: true, forcedJSONParsing: true, clarifyTimeoutError: false}url: "/inApp/web/getMessages"validateStatus: ƒ (t)validation: {params: bt}xsrfCookieName: "XSRF-TOKEN"xsrfHeaderName: "X-XSRF-TOKEN"[[Prototype]]: Objectmessage: "Network Error"name: "AxiosError"request: XMLHttpRequestonabort: ƒ ()onerror: ƒ ()onload: nullonloadend: ƒ y()onloadstart: nullonprogress: nullonreadystatechange: nullontimeout: ƒ ()readyState: 4response: ""responseText: ""responseType: ""responseURL: ""responseXML: nullstatus: 0statusText: ""timeout: 0upload: XMLHttpRequestUploadonabort: nullonerror: nullonload: nullonloadend: nullonloadstart: nullonprogress: nullontimeout: null[[Prototype]]: XMLHttpRequestUploadwithCredentials: false[[Prototype]]: XMLHttpRequestDONE: 4HEADERS_RECEIVED: 2LOADING: 3OPENED: 1UNSENT: 0abort: ƒ abort()getAllResponseHeaders: ƒ getAllResponseHeaders()getResponseHeader: ƒ getResponseHeader()onreadystatechange: (...)open: ƒ open()overrideMimeType: ƒ overrideMimeType()readyState: (...)response: (...)responseText: (...)responseType: (...)responseURL: (...)responseXML: (...)send: ƒ send()setAttributionReporting: ƒ setAttributionReporting()setPrivateToken: ƒ setPrivateToken()setRequestHeader: ƒ setRequestHeader()status: (...)statusText: (...)timeout: (...)upload: (...)withCredentials: (...)constructor: ƒ XMLHttpRequest()Symbol(Symbol.toStringTag): "XMLHttpRequest"onabort: (...)onerror: (...)onload: (...)onloadend: (...)onloadstart: (...)onprogress: (...)ontimeout: (...)get onreadystatechange: ƒ onreadystatechange()set onreadystatechange: ƒ onreadystatechange()get readyState: ƒ readyState()get response: ƒ response()get responseText: ƒ responseText()get responseType: ƒ responseType()set responseType: ƒ responseType()get responseURL: ƒ responseURL()get responseXML: ƒ responseXML()get status: ƒ status()get statusText: ƒ statusText()get timeout: ƒ timeout()set timeout: ƒ timeout()get upload: ƒ upload()get withCredentials: ƒ withCredentials()set withCredentials: ƒ withCredentials()[[Prototype]]: XMLHttpRequestEventTargetstack: "AxiosError: Network Error\n at m.onerror (chrome-extension://chibhalopjikkeoammpnjladjhoeemon/retailer.js:2:332303)\n at se.request (chrome-extension://chibhalopjikkeoammpnjladjhoeemon/retailer.js:2:340000)"[[Prototype]]: Errorconstructor: ƒ X(t,e,n,r,i)from: (t,e,n,r,i,a)=> {…}ECONNABORTED: "ECONNABORTED"ERR_BAD_OPTION: "ERR_BAD_OPTION"ERR_BAD_OPTION_VALUE: "ERR_BAD_OPTION_VALUE"ERR_BAD_REQUEST: "ERR_BAD_REQUEST"ERR_BAD_RESPONSE: "ERR_BAD_RESPONSE"ERR_CANCELED: "ERR_CANCELED"ERR_DEPRECATED: "ERR_DEPRECATED"ERR_FR_TOO_MANY_REDIRECTS: "ERR_FR_TOO_MANY_REDIRECTS"ERR_INVALID_URL: "ERR_INVALID_URL"ERR_NETWORK: "ERR_NETWORK"ERR_NOT_SUPPORT: "ERR_NOT_SUPPORT"ETIMEDOUT: "ETIMEDOUT"length: 5name: "X"prototype: Error {isAxiosError: true, toJSON: ƒ}constructor: ƒ X(t,e,n,r,i)toJSON: ƒ ()isAxiosError: true[[Prototype]]: Objectsuper: {name: 'Error', message: '', toString: ƒ}arguments: (...)caller: (...)[[FunctionLocation]]: retailer.js:2[[Prototype]]: ƒ ()[[Scopes]]: Scopes[4]toJSON: ƒ ()isAxiosError: true[[Prototype]]: Object
retailer.js:2 GET https://api.iterable.com/api/inApp/web/getMessages?count=1&packageName=donation-reminder&platform=We... net::ERR_FAILED 429 (Too Many Requests)
(anonymous) @ retailer.js:2
xhr @ retailer.js:2
ne @ retailer.js:2
Promise.then
_request @ retailer.js:2
request @ retailer.js:2
(anonymous) @ retailer.js:2
t.baseIterableRequest @ retailer.js:2
t.requestInAppMessages @ retailer.js:2
(anonymous) @ retailer.js:2
f @ retailer.js:2
(anonymous) @ retailer.js:2
(anonymous) @ retailer.js:2
e @ retailer.js:2
s @ retailer.js:2
(anonymous) @ retailer.js:2
(anonymous) @ retailer.js:2
(anonymous) @ retailer.js:2
t.getInAppMessages @ retailer.js:2
(anonymous) @ retailer.js:2
(anonymous) @ retailer.js:2
(anonymous) @ retailer.js:2
zu @ retailer.js:2
o @ retailer.js:2
(anonymous) @ retailer.js:2
(anonymous) @ retailer.js:2
(anonymous) @ retailer.js:2
Promise.then
(anonymous) @ retailer.js:2
(anonymous) @ retailer.js:2
(anonymous) @ retailer.js:2
zu @ retailer.js:2
o @ retailer.js:2
Promise.then
zu @ retailer.js:2
o @ retailer.js:2
Promise.then
zu @ retailer.js:2
o @ retailer.js:2
Promise.then
zu @ retailer.js:2
o @ retailer.js:2
Promise.then
zu @ retailer.js:2
o @ retailer.js:2
(anonymous) @ retailer.js:2
(anonymous) @ retailer.js:2
Cd @ retailer.js:2
VM7534:1 GET https://dyn-img.com/i/plusnet.js net::ERR_ABORTED 404 (Not Found)

There are LOTS of console errors reported ... and why does the site attempt to connect to FaceBook to name but one?

[#12]

Thanks for taking the time to supply that info, @Townman 

I've added it to the ticket.

James

[#13]

@James_B 

I am now into watching everything.  I logged into a fresh session on the iPhone.  Notifications Count was 94 (92 + 2).  Looked at a numbers of posts, but made none.

I then observed that the count fell to 42 + 2 (same 50 difference reported above) with no obvious apparent cause or action from me.  I did though note a close time toaster pop-up.

They can be unpredictable, not necessarily appearing contemporaneously with the event giving rise to them.  They have been observed as being late and getting repeated.  Could that mechanism have any bearing on the observed experience?

[#14]

Hmm case in point.

Just after making the above post, I received another REPLY toaster pop-up after which the count decreased by 1.  One might have expected a reply to increment the notification count.

I am staying clear of the notifications page so that no Bulk action by me clears counts.  I guess that if I stumble a cross a replied to topic, that might remove counts for that thread.

[#15]

@James_B 

FWIW subsequent to the PM reply, I have now hit the 101 non-PM notification count.

Should I refrain from zeroing the count to permit further investigation or do I just accept that the vendor has neither the interest or the capability (skill) to bottom this out?

It ought to be a simple enough request to find the current counts of reply / mention / thanks notifications and then work out which bit of the system in what circumstances ignores part of the total count.

For someone with access and competence it’s a 5 minute SQL query job.