Notification V2 - "500 server error"

What product/components do you use and which version/fix level are you on?

Version: 1013.0.260

Is your question related to the free trial, or to a production (customer) instance?

production instance

What are you trying to achieve? Please describe it in detail.

Notification V2

Do you get any error messages? Please provide a full error message screenshot and log file.

Yes, see the text below.

Have you installed all the latest fixes for the products and systems you are using?

Not sure.

Hi all,

We are currently trying Notification V2. We are having the following issue after we sent a http WSS request to open the websocket:

HTTP/1.1 500 Server Error
Date: Mon, 26 Sep 2022 15:00:30 GMT
Content-Type: text/html;charset=iso-8859-1
Content-Length: 709
Connection: keep-alive
Cache-Control: must-revalidate,no-cache,no-store
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000; includeSubDomains

<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 500 Failed to create producer/consumer: Policies not found for t1059969044/relnotif namespace</title>
<body><h2>HTTP ERROR 500 Failed to create producer/consumer: Policies not found for t1059969044/relnotif namespace</h2>
<tr><th>MESSAGE:</th><td>Failed to create producer/consumer: Policies not found for t1059969044/relnotif namespace</td></tr>
<hr><a href=>Powered by Jetty:// 9.4.42.v20210604</a><hr/>


I strongly suspect that that the notification V2 is not deployed on my tenant with version 1013.0.260. It used to work on the trial tenant but somehow it doesn’t work for the tenant with version 1013.0.260. I don’t have any clue about this “error” since I didn’t find anything in Cumulocity documentation.

It would be very appreciated if you can help us.


What are the tenants involved here?

It is as the following:

Same error on our tenant. Is this notification2.0 not generally available on


The Cumulocity R&D and Cloud Operations teams are investigating this issue. We will provide more information here as we have it.



A 500 internal server error is, as the name implies, a general problem with the website’s server. More than likely, this means there’s an issue or temporary glitch with the website’s programming


Hi Will,

It has been successfully resolved by R&D team.


This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.