Hello Herin,
Two recommendations:
1. The alarm will be published if spooler probe fails to create new queue file(q1.rdb/q2.rdb).
The cause is generally lack of disk space, disk problem, Anti-Virus stops disk i/o, and so on. User needs to fix the system side problem, the restart UIM robot for recover from the problem.
2. The Hub Configure -> Robots -> Inactive Robot Setup Severity setting was set to "no alarms".
If this does not help please raise a support case for further investigations.
Kind regards,
Britta Hoffner