It has been noticed that some robots in the environment are generating unavailability alerts. After verification, it turned out that the robot.cfg files for those robots are corrupted:
DX UIM 23.4.X
The robot is unable to start due to robot.cfg corruption
The best practice is to regularly back up the Nimsoft directory (or the most crucial .cfg files, like robot.cfg, controller.cfg, data_engine.cfg etc.). This will help to prevent/mitigate the long-term outage.
The solution for such an issue is to quickly revert to the backup of the robot.cfg file and start the services.