Hi, I am trying to set up a Connection Server and stumbled over the following question, which was not really answered via the HelpCenter: Can I use a Connection Server with offline storage capability? In case ThingWorx goes down, does the Connection Server persist data and synchronises it once ThingWorx is up and running again? During the ThingWorx outage, the Thing itself is unable to send data to ThingWorx. I would somehow expect, that the Connection Server would be able to take the data and pass it on to the ThingWorx server at a later point, once all services are up and running again. Thanks, Michael

16-Pearl

Solved

Connection Server questions

Forum|Forum|7 months ago
August 28, 2025
1 reply
795 views

Hi,

I am trying to set up a Connection Server and stumbled over the following question, which was not really answered via the HelpCenter:

Can I use a Connection Server with offline storage capability? In case ThingWorx goes down, does the Connection Server persist data and synchronises it once ThingWorx is up and running again?

During the ThingWorx outage, the Thing itself is unable to send data to ThingWorx.

I would somehow expect, that the Connection Server would be able to take the data and pass it on to the ThingWorx server at a later point, once all services are up and running again.

Thanks,

Michael

Connectivity

Best answer by Rocko

Connection Server can not do that.

From the documentation:

If all ThingWorx instances are either not connected or not writable, request messages result in an exception being returned. For the Connection Server, the result is a 500 Internal Error response being sent to the edge device.

When a Connection Server is disconnected from all ThingWorx instances, all Edge WebSockets are closed. However, the Connection Server does not prevent a new Edge WebSocket from connecting.

Kepware can do some buffering, but if you work with Edge Devices, you would have to do the buffering on that device.

Rocko

Answer

19-Tanzanite

Connection Server can not do that.

From the documentation:

If all ThingWorx instances are either not connected or not writable, request messages result in an exception being returned. For the Connection Server, the result is a 500 Internal Error response being sent to the edge device.

When a Connection Server is disconnected from all ThingWorx instances, all Edge WebSockets are closed. However, the Connection Server does not prevent a new Edge WebSocket from connecting.

Kepware can do some buffering, but if you work with Edge Devices, you would have to do the buffering on that device.