An alert email was received for a device, but checking Web Admin shows no matching alert event, or the alert list looks empty for that device.
Two Things Generate Alert Emails
Print Tracker has two separate alert sources.
Supply alerts. Configured by the dealer in Web Admin. These fire on toner percentage thresholds or estimated depletion calculations.
Service alerts. Generated from the device's own service event log, read over SNMP or from its web server. These reflect conditions the device firmware reports itself, such as a paper jam, a door left open, or service required.
Where to Look
Both types are logged in the same place.
Fleet-wide: go to Devices, then Manage alerts. The log shows Timestamp, Entity, device details, Description, Supply Levels, and Status. You can set a date range, include child entities, filter, choose columns, and export. A red bell marks an active alert and a New badge marks a recent supply replacement.
One device: go to Devices, then View devices, expand the device, click settings, and open its Device Alerts tab.
Start with the date range on the Manage alerts screen. It defaults to a recent window, so an alert older than that window is simply outside the view rather than missing.
Step 1: Check at the Device Level
Open the device in Web Admin.
Open the Alerts tab.
Look for an event whose timestamp matches when the email arrived.
Step 2: The Alert May Have Auto-Resolved
This is the most common explanation. If the condition cleared itself quickly, for example a toner reading spiked and returned to normal, or a jam was cleared, the event may already be resolved by the time you look, and resolved alerts are hidden by default.
Below the supply alert history, select View resolved alerts.
A transient toner reading is worth following up separately, because it can also create a false replacement record. See Toner Level Spike Causing Incorrect Toner Replacement Record.
Step 3: Current State Versus State at Alert Time
Web Admin shows a device's current state, based on the most recent data received. If the device has reported newer data since the alert, the screen reflects the newer state, not the state that triggered the email.
So a device showing healthy toner does not contradict a low toner email from two days ago. To see the state at the time, use the meter history instead: Devices, then View devices, click the three-dot menu next to the device in question, then View meter history.
If the Event Is Genuinely Missing
If you have checked the device Alerts tab, included resolved alerts, and widened the date range, and there is still no matching event, that may indicate a logging inconsistency worth reporting.
Contact Print Tracker support with:
The full text of the alert email, or a screenshot
The timestamp of the email
The device IP address and serial number, if the email includes them
The dealer and entity name
The email itself is the important artifact here, since it is the only record of the alert that you know exists.
Related Articles
Missed Low Supply Alert: Why a Toner Alert Did Not Arrive, for the reverse problem
Setting Up Device Alerts (Supply, Service, and Volume)
Estimated Depletion Alerts: Why They Fire at High Toner Level
