It Only Fails Under a Condition Nobody Noticed: A Decision Tree

Why this matters

The customer says it just fails whenever it feels like it. No pattern. That report is almost never true. It means the trigger sits outside their awareness, not that there is no trigger. The faults that eat the most time are the ones where nobody, including you at first, can name the condition. This tree is about exposing a condition no one has noticed yet, which is a different job from reproducing one you already suspect.

Start here: "random" means unnoticed, not absent

When a customer says there is no pattern, hear it as "the pattern is outside what I watch." People notice what they do on purpose. They do not notice a voltage dip, a dew point, an automated pump cycle, or a neighbor's equipment. So do not argue about whether a trigger exists. Assume one does and go looking where their attention was not.

Safety first: if a protective device keeps operating, respect it

Before hunting, handle the hazard case. If the intermittent is an electrical fault, a fuel or combustion symptom, or a safety device that keeps operating (a breaker, GFCI, relief valve, high-limit, or float switch that trips and resets), treat every operation as a real response to a real condition. Do not defeat, jumper, or repeatedly reset a protective device to "get past" the intermittent so you can watch it. De-energize or shut off to work, verify the hazard is controlled, and hunt the trigger with the protection left intact. A device that trips on an unnoticed condition is doing exactly its job, and the trip is your best clue.

Branch 1: re-interview around the un-obvious

The first pass usually asked the wrong questions. Ask these instead:

• What here runs on a timer or a schedule? Irrigation, recirculation pump, pool cleaner, defrost, setback thermostat, vehicle charging. Customers forget automated things exist.
• What did you most recently add or change, even months ago, even something unrelated? A new appliance, an added circuit, landscaping over a buried line.
• Who else is here, and when? A cleaner, a tenant, kids home from school, a night-shift schedule.
• Does it track the calendar or the weather at all, even loosely?

One of these surfaces the trigger more often than any meter does.

Branch 2: instrument and wait

When the interview yields nothing, make the invisible visible. Leave a data logger on the most likely variable (voltage, temperature, pressure, or runtime), or give the customer a structured log to fill in. Capture both failures and normal periods so you have something to compare. You are building the record the equipment did not keep for you.

Branch 3: sweep one variable at a time

If you can stay or return, provoke it deliberately. Vary a single condition while holding the rest steady: heat it, load it, run the suspected companion appliance, dampen it safely. Change one variable per trial. Change two and a failure tells you nothing about which one caused it. The discipline of one-at-a-time is what separates a discovery from a coincidence.

Branch 4: widen the boundary

If nothing on the property correlates, look past the property line. Utility voltage and time-of-use switching, pressure on a shared water main, a shared neutral with a neighbor, or electrical noise from nearby heavy equipment can all drive a fault that has no on-site cause. When the building is clean, the condition may be arriving from outside it.

Recap

1. Read "random" as "unnoticed." Assume a trigger exists.
2. If a protective device keeps operating, respect it, work de-energized, and read the trip as data.
3. Re-interview around automated schedules, recent changes, other people, and season or weather.
4. If the interview is dry, instrument and wait, then sweep one variable at a time.
5. If the property is clean, widen the boundary to shared infrastructure.

References

• Trade-standard intermittent-fault diagnosis practice
• NFPA 70E principles for working safely around protective devices and energized equipment
• See related: Finding the Hidden Trigger Behind an On-and-Off Fault; Using a Timeline to Expose a Hidden Trigger