• Check if the lastConnection property of the Thing is updating. If it does not update, refer to Observation 2: The lastConnection property of the Thing does not update.

• Verify that the Connector is still running or attached. To do this, navigate to the Monitoring > Connection Servers page and validate that the Connector is available in the list.

• Verify if the assetLogEvents property exist on the Thing and if the Axeda Compatibility Extension is installed. Check if the Thing was created using an Axeda*Model Thing Template. If yes, the assetLogEvents property would have automatically been created.

• Check if the WritePropertyError advisory event was sent to the Connection Services Hub. This event indicates that the Connector attempted to write a property for a Thing, but could not do it because of a problem. The events for the Connection Services Hub are listed and briefly described in the topic, Event Notifications.

• If you are running a multi-node connector environment, verify that all the Connectors still running or attached.

• Check the Monitoring > Connection Servers page and validate that the correct number of connectors are available in the list. If all the Connectors are not displayed in the list, then traffic could land on a broken connector and it does not reach ThingWorx Platform.

• Monitor metrics from the Connector nodes to validate that each eMessage Connector is processing messages from the load balancer. For more information, refer to Metrics Monitoring.

• Review logs from each connector node and validate that it has not disconnected from the ThingWorx Platform. If exceptions are present, refer to Exceptions Observed in the Log for eMessage Connector.

• Use a packet sniffer to validate that network packets are being sent:

◦ Between the load balancer and each connector node.

◦ Between each connector node and ThingWorx Platform.

• Review the Connector logs to determine if any exceptions are present. If exceptions are present, refer to Exceptions Observed in the Log for eMessage Connector.

• Check if the Connector has stopped processing messages from agents completely. For more information, refer to Observation 11: Connector stops processing agent messages completely.