The inactive 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 inactive 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.
An inactive state happens when the system is online and the mining client is mining, but there is no speed (i.e, speed is 0 H/s). Such an event can happen because of the wrongly configured pool, wrong authentication on the pool, wrong port, or a hardware error in ASIC. You can do several different actions for an inactive trigger: restart the mining client, reboot the machine, shut down the machine, and call a webhook.
If the inactive state is a result of hardware error in ASIC, we see that usually rebooting the ASIC helps. However, if you are getting too many inactive triggers, you should examine your hardware.
If the inactive trigger is fired for the wrong configuration reason, you should examine your worker's config or if you have a profit switch turned on, check the profit switch configs. Check if you have correctly set algorithm parameters, a port on the pool, stratum type, and authentication method.
Was this article helpful?