This alarm is caused by the robot not being able to connect to the hub.
The robot then spools up alarms and QoS messages.
When connectivity is restored, the alarms are received.
Checking customers' alarms we have seen that this alarm is generated at a fixed frequency.
In a short time the alarm usually clears.
Since the robot is queuing messages no information is being lost.
The alarm can be ignored, but it does indicate some form of connectivity issue.