The Local Fault Log Was Cleared Before You Arrived, Decision Tree

Why this matters

You go to pull a unit's fault history and it is empty, or nearly empty, on equipment that has clearly been having problems for a while. That is either a coincidence, an innocent side effect of something unrelated, or a sign someone cleared it, possibly to hide a diagnosis they could not complete or a fix that did not work. Assuming the worst burns a relationship with a customer or a referring contractor over a misread. Assuming nothing happened means you lose the one piece of evidence that would have told you what already failed to fix this.

Start here: do not assume malice, but do not ignore the gap either

A cleared or suspiciously empty log is a finding to investigate calmly, not an accusation to make out loud. Approach it the same way you would approach any other missing evidence: note it, consider the ordinary explanations, and adjust your diagnostic approach around the fact that you have lost a resource, without announcing a theory about who cleared it or why until you actually know.

Step 1: Confirm the log is actually empty, not just hard to read

Before concluding anything was cleared, make sure you are reading the history correctly. Some controls require a specific sequence to display older entries, some split history across more than one location on the same unit (a main board and a separate protective relay, for example), and some display only the single most recent fault by default with older entries requiring a deeper menu. Rule out that you are simply not seeing the full record before assuming it was wiped.

Step 2: Consider the ordinary, non-suspicious reasons for a clean log

Several innocent things can produce a genuinely empty or unexpectedly clean history:

• A recent power loss long enough to clear an unbacked memory, on controls that do not retain history through a power interruption. Check whether the specific control's documentation says it retains through power loss at all.
• A board or control replacement, where the new component starts with no history because it is, in fact, new. Check the physical part for signs of being newer than the rest of the unit.
• A recent factory reset performed for an unrelated, legitimate reason (a full reconfiguration, a firmware update, a different repair that required a reset as a documented step).
• The unit is genuinely new to this problem and the log is clean because nothing has happened yet worth logging, and the current symptom is the very first occurrence.

Step 3: Look for corroborating evidence of prior work, regardless of what the log shows

Whether or not the log was cleared, check for physical signs of recent prior attention: fresh wire nuts or connectors, a component that looks newer than its surroundings, tool marks, a panel not fully reseated, or a customer mentioning "someone was out here a few weeks ago." A cleared log combined with visible signs of recent, undocumented work is a much stronger signal than either alone.

Step 4: If it looks like a genuine prior-contractor situation, ask the customer directly and neutrally

"Has anyone else been out to look at this recently?" is a completely reasonable, neutral question that often surfaces exactly what happened, a prior company that could not fix it, a reset performed as part of an incomplete repair, or a DIY attempt. Most customers will tell you plainly once asked directly, and this is far more productive than speculating from the equipment alone.

Step 5: Treat the loss of history as a real diagnostic constraint, and say so

However it happened, a cleared history means you have lost the count, the timing, and the pattern that would normally speed up this diagnosis. Do not pretend this does not matter. Tell the customer plainly: "The fault history on this unit is clear, which means I can't see what's happened before today. I'm working from today's symptoms only, which may take a bit longer to pin down." This sets an honest expectation instead of quietly working with less information than a customer would assume you have.

Step 6: Start building a new baseline from this visit forward

Since the old record is gone, treat today as day one of a fresh history. Document what you find in detail, note the exact reading at the time of your visit, and if the fault is not fully resolved today, that record becomes the foundation the next visit builds on, so the same loss of information does not repeat a second time.

Recap

1. Confirm the log is genuinely empty, not just hard to access.
2. Consider ordinary explanations: power loss, a board replacement, a legitimate reset, or a truly new problem.
3. Look for physical evidence of prior undocumented work regardless of the log.
4. Ask the customer directly and neutrally whether anyone else has been out.
5. Acknowledge to the customer that the missing history is a real constraint on today's diagnosis.
6. Build a thorough new baseline record starting from this visit.

References

• Manufacturer documentation for a specific control's memory retention behavior through power loss and reset
• See related: What a Lockout Count Tells You That a Single Visit Can't; Reading a Unit's Own Local Fault History, Not a Connected System