The Issues Page gives you a comprehensive, real-time view of every problem affecting miners in your current client. Instead of manually hunting for underperforming or unhealthy hardware, Foreman automatically surfaces issues so you can monitor, investigate, and act quickly.

The page is designed to help you understand fleet health at a glance while also allowing you to drill down into specific problems and affected miners.

Miner Status Overview

Miner status provides a high-level snapshot of your fleet health.

A pie chart displays the percentage of miners in each status category across your client.

Standard Miner Statuses

These statuses are consistent across all clients:

• Active — Miner is online and reporting metrics normally
• Inactive — Miner is not currently active or reporting expected activity
• Offline — Miner is not sending metrics or is unreachable
• Warning — Miner is reporting abnormal or degraded performance
• Error — Miner is experiencing a critical issue affecting performance or connectivity

These statuses help you quickly assess overall fleet stability before diving into specific issues.

Miners Needing Attention

This metric shows the proportion of miners currently experiencing at least one issue.

• It is displayed as: Miners with Issues / Total Miners

This provides an immediate sense of how widespread problems are across your fleet.

Issues Table

The Issues Page is built around a table that organizes all detected issues in your fleet. Issues are automatically generated based on miner metrics collected by Pickaxes and evaluated by Foreman’s processing layer.

The core of the page. Each row represents a distinct issue affecting your miners, with the following columns:

• Issue — a description of the problem
• Warning — number of miners showing early signs of the issue
• Failing — number of miners actively experiencing the issue
• Actions — available next steps for that issue

Taking Action

From the Issues Page, you can take immediate action on identified problems:

• Filter Issues: Narrow the view to focus on specific issue types, severity levels, or affected groups.
• Show Miners: Click any issue to open a filtered view of all miners associated with that issue on the Miners Page. This allows for fast investigation and troubleshooting.
• Export the current Issues Table as a CSV file for offline analysis, reporting, or record-keeping.

How Issues Are Detected

Two Types of Issues

Foreman supports two categories of issues:

System Issues

System Issues are predefined conditions automatically monitored across all fleets. These cover common failure states and hardware anomalies without requiring configuration.

→ Abnormal Hashrate
Triggered when a miner reports a hashrate significantly outside the expected range.

• Flags when hashrate exceeds ~3x nameplate hashrate

→ Duplicate MAC Address
Triggered when two miner records share the same MAC address.
Common causes include manual entry duplication, overlapping Pickaxe sync ranges, or misconfigured network scans.

→ Fan Speed Too High
Triggered when the reported fan speed exceeds configured thresholds.

• Clears automatically once values return to normal

→ Fan Speed Too Low
Triggered when the reported fan speed falls below configured thresholds.

• Clears automatically once values return to normal

→ Hardware Errors Exist 
An older Antminer indicator built to catch hashboard errors. It has limited reliability on modern hardware, but accuracy can be improved by creating custom issues with more specific error code criteria to better target your setup.

→ Hash Rate Too Low
Triggered when a miner’s hashrate drops below its configured expected range (set per miner).

→ Invalid Pool Configuration
Triggered when a miner’s pool configuration does not match trusted pool settings.
This includes mismatches in stratum, worker naming, or regex-based validation rules across client-level trusted pool configurations.

→ Miner Not Updating (core offline detection family)
Triggered when no metrics are received from a miner within a defined window (typically ~5 minutes).

• May stack with other “not updating” states
• Can occasionally reflect false positives depending on Pickaxe configuration

→ Miner Not Updating (Recent)

• Triggered after ~5 minutes without metrics
• Time-boxed to 1 hour
• Clears automatically after recovery or timeout
• Designed to detect early-stage issues quickly

→ Miner Not Updating (1 Day)
Triggered when no metrics are received for 24 hours.

• Continues to stack while the issue persists

Miner Not Updating (2 Days)
Triggered when no metrics are received for 48 hours.

• Continues to stack while the issue persists

→Miner Not Updating (Forever)
Triggered when a miner has never successfully reported metrics.

• Typically occurs with manually added miners that never connected

→ No Pools Configured
Triggered when no pool data is reported from a miner.

• Often resolves automatically after Pickaxe sync or configuration updates

→ No Shares Being Submitted
Triggered when a miner reports no change in share counts over five sequential check-ins.

→ Pickaxe Offline
Triggered when a Pickaxe device becomes unreachable and cannot collect or transmit metrics.

→ Temperature Sensor Too High
Triggered when reported hardware temperature exceeds safe thresholds.

→ Zero Hash Rate
Triggered when a miner reports zero hashrate while still appearing active.

Custom Issues

System Issues cover the most common problems Foreman watches for out of the box — but every operation is different. With Custom Issues, you can define your own conditions and thresholds to monitor exactly what matters to your fleet.

       → Check out our Custom Issues guide to learn how to set them up.

Have more questions? Submit a request below or reach out to the customer success team directly — we're happy to help.