The idle triggers audit is available under the activity tab in the diagnostic and shows the current grade from the data obtained yesterday and a small historical chart for the performance of the last week. The grade is determined depending on how many idle triggers were fired. The more triggers per worker, the lower the grade.
Triggers are the most important mechanism that is keeping your mining operation in good health. However, firing too many triggers just isn't efficient.
Idle state happens when the system is online, but the mining client isn't mining. Usually, it is caused by incorrect config where mining client is running but shows an error instead of mining. It can also happen if the worker stopped mining (either by some other trigger or manual action). You can do several different actions for idle trigger: restart mining client, reboot the machine, shut down the machine, and call a webhook.
If you are getting too many idle triggers, check what is going on with your config. If you have a profit switch turned on, check the configs there as well. The config can be quickly examined by checking the console or the latest activity log. Additionally, you can also check if the idle state is being triggered by some other trigger.
Was this article helpful?