Subscription failed - NodeRED

[Tamer]

Hello,

After one or two hours of operation, NodeRED loses the connection (below). I also noticed when I browse to the Datalayer from the main ctrlX dashboard that it takes forever for the Datalayer to populate (below). Doing a power cycle to ctrlX fix the issue. For context, I was following the 'Getting started with InfluDB' from the How-To videos.

I have checked my session policies as recommended on another post, and it is set to unlimited (below).

The ctrlX I am using has been upgraded to 'X3_Systemimage_1.20.12' and 'DC_App_Paket_0120.6'. I also have a permenant licence for NodeRed, and a 10 days trial licence for the other IOT apps.

If anyone has similar experience solving this issue, please share.

[MauroRiboniMX]

Hello, 

Thanks for posting. How "fast" is the subscription? does it happen also if you substitute the subscription with a triggered request? Just to test if it is a subscription problem and if that can be a possible workaround. 

Can you create also a system report? 😃

Mauro 

[Tamer]

Hello Mauro,

Thank you for your reply.

I took two reports, one while the subscription was runnning, the other after it froze, and the latter showed below errors while creating the report.

The subscription publish interval is set to 10s (10000).

I tried an inject node triggering a datalayer request (below), and it works, but it takes longer than usual to process (few seconds).

[MauroRiboniMX]

Sorry for the late answer. I analyze if i can find something special otherwise i open a bug. thanks 

[MauroRiboniMX · Accepted solution]

Can Be a problem regarding the ctrlx-automation node used. we're trying if updating that the problem is solved

[MauroRiboniMX]

Hello @Tamer , 

Have you tried to update the ctrlx-datalayer node as discussed? 😊

[Tamer]

Hi Mauro,

Yes, I updated the NodeRed ctrlX pallet as per your recommendation (still v1.20), and it is now working fine 😊

Thanks for your help.