+9After upgrade to 24R1 i receive this information toaster message occasionally. I always get them when i log in, and then approximately one time each 10 minute. Message says “Unable to subscribe to notifications. You will not receive new notifications”. However i do still receive notifications. This issue is from a customer environment, and i have not seen it in other environments on 24R1. At least some other users have the same issue.
Any ideas on why i get this message?
+9You can resolve this by enabling the `client-notification-services` pod in your `values.yaml` file. Update it as shown in the example below and re create the name space
ifsappclientnotification:
replicas: 2
+9Case CS0236676 was created to handle this issue.
+3You can resolve this by enabling the `client-notification-services` pod in your `values.yaml` file. Update it as shown in the example below and re create the name space
ifsappclientnotification:
replicas: 2
Hello, this doesn´t work for us, we use 2 replicas for this pod but still get such messages.
+14Suggested solution didn't work, any other idea?
Dear all,
We are still facing the same issue and are currently on APP10 UPD24. Does anyone have any suggestions on where to look or what to do?
Thanks,
Bram
+5Hi,
The issue has already been reported to the Product Development team, and the planned resolution is currently targeted for IFS version 24R2 EA.
Please note that this information is for planning purposes only and is subject to change.
Once the issue is resolved, we will confirm the specific update that includes the fix.
Regards,
Thushanthy
Hi,
The issue has already been reported to the Product Development team, and the planned resolution is currently targeted for IFS version 24R2 EA.
Please note that this information is for planning purposes only and is subject to change.
Once the issue is resolved, we will confirm the specific update that includes the fix.
Regards,
Thushanthy
Hi Thushanthy,
has this issue been resolved in Apps10?
thanks
Gary
+11
To be quite honest I don’t know, we’re on Managed Cloud by IFS, so we don’t handle any of the middleware/infrastructure ourselves.
Also having this problem after 25R1 SU1 deploy. Can you please suggest how to get rid of it by setup on proxy sever? We have on-premise IFS Cloud version. Thank you
Hi,
We have just upgraded to 25R1 and we have the message too.
If anybody has information, it will be appreciated.
Thanks and Regards,
Anne-Sophie
+1We just upgraded from 24R1 to 25R1 and are now getting this message as well. We were not getting this message when on 24R1.
Hi, I created a case to IFS on this issue and they answered that this issue will be fixed in 25R1 SU3 that will be released on August 21. Hope it helps.
+23We are in 25R1 SU3 [in CFG and UAT] and we are getting it since yesterday, time to time.
Our IFS partner, together with the hosting partner, did increase the header default size in the load balancer yesterday. I thought I am seeing this message after that only.
Any ideas?
+23According to IFS support case CS0445795, the issue is fixed via 25R1 SU5 onwards. I don't have other RU / SU information unfortunately.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
