Etienne

It is possible that the server you are connecting to does not implement the ResendRequest method. We have identify a bug that causes subscription reconstruction to not be working properly...

During reconnection with a new run of the server, NodeOPCUA is trying to restore the MonitoredItem that was created in the previous instance automatically. The log shows that the createMonitoredItem...

You can investigate the defaultMaxMonitoredItemsPerCall by using an OPCUA Client and visiting the following node in the address space: `Objects/Server/ServerCapabilities/OperationalLimits/MaxMonitoredItemsPerCall`  I suspect that MaxMonitoredItemsPerCall is zero (0), meaning there...

This requires further investigation with a physical connection to the device, which cannot be conducted on a public forum. I suggest you contact sterfive Support through your [NodeOPCUA Support membership](https://support.sterfive.com)...

now merged into master

> What about listening for `terminated` event and recreate the subscription if needed? Also what about the warning posted above? It's not clear what I should fix on code The...

> What does happen when the subscription reaches the max keepalive? The subscription sends an empty PublishResponse with no data change notification into it, The client then sends a new...

It should be fixed now in [[email protected]](https://github.com/node-opcua/node-opcua/releases/tag/v2.120.0). @AcureroAdrian can you confirm ?

Fixed in [[email protected]](https://github.com/node-opcua/node-opcua/releases/tag/v2.121.0)

Closing due to no activity