Customer Reset It Repeatedly, Now It Is Stuck: Decision Tree
Why this matters
The system threw a fault, the customer reset it, it ran, it faulted again, they reset again, and somewhere in that loop it stopped responding entirely. Now it is stuck: a hard lockout, a tripped non-resettable device, or a component that finally gave out from being cycled into a fault it was protecting against. The customer wants you to "just reset it one more time," but the system locking out is the design working, not the design failing.
The diagnostic trap is to treat the lockout as the problem. It is not. The lockout is the system refusing to keep doing the thing that was damaging it. The customer's repeated resets defeated the protection over and over until either the controller latched permanently or the underlying fault caused collateral damage. Your job is to find what the system was protecting itself from, not to clear the count and hand it back.
Every trade has this: a furnace that locks out after repeated ignition-failure resets, a well pump in a repeated thermal-overload reset, a GFCI reset over and over against a real ground fault, a dishwasher reset through repeated overfill conditions.
Symptom presentation
The signature is a fault that escalated from intermittent and resettable to permanent and stuck. Early in the loop the customer could clear it. Later they could not. That escalation is the key data point: a protective system that latches after a set number of trips is telling you the fault was real and recurring, not a glitch.
A second presentation is collateral damage. Repeated resets force a component to keep operating in a fault condition. A motor cycled against a locked rotor overheats. An ignition system cycled against no flame floods or fatigues. A pump cycled dry scores its seals. The original fault may now be accompanied by a damaged part the resets created.
Quick checks
- Is the system in a hard lockout (manual reset required, fault latched) or merely off? Hard lockout means the protection counted real trips.
- How many resets did the customer perform, and over what time? Many resets in a short window means the fault recurred fast, which narrows the cause.
- Is there a stored fault code or trip indicator? Read it before clearing anything.
- Is there evidence of collateral damage from repeated cycling: heat discoloration, burnt smell, worn seals, tripped one-time device? The resets may have created a second fault.
Isolation tree
Step 1: Read before you reset. Capture every fault code, trip flag, and indicator the system stored. The reset count and last-fault code tell you what the system was fighting. Clearing it first destroys evidence.
Step 2: Identify the protected-against condition. A lockout always names a hazard by its trigger: no ignition, no flame, overcurrent, overtemperature, ground fault, overpressure, low water. Map the lockout type to the condition it guards. That condition is your real fault.
Step 3: Reproduce the trip safely. Restore the system to a state where it will attempt to run, and watch for the trigger condition on the first attempt. The first attempt after a lockout is the cleanest look at the original fault because it has not yet been muddied by another reset.
Step 4: Find the root of the trigger. No ignition points to fuel, spark, or air. Overcurrent points to a mechanical bind, a short, or a load fault. Ground fault points to insulation or moisture. Overtemperature points to airflow, load, or cooling. Trace the trigger to its cause.
Step 5: Assess collateral damage. Inspect the components that were cycled in the fault condition. Repeated resets often add a second failure on top of the first. Decide what needs replacement versus what is sound.
Confirming diagnosis
The diagnosis is confirmed when you can name the condition the lockout protected against, demonstrate it on a controlled run attempt, and trace it to a root cause. ISO 13379-1 root-cause logic treats a protective trip as a diagnostic signal, not noise: the trip parameter directly indicates the fault class.
You also confirm whether the resets caused collateral damage by inspecting the cycled components for fault-condition wear. If found, you now have two findings: the original trigger and the reset-induced damage.
Do not clear a lockout and return the equipment to service without finding the trigger condition. A lockout that you simply reset will trip again, and each repeated trip can push the system closer to fire, flooding, or electrocution. Repeated manual resets of a tripped GFCI, overcurrent device, or flame-safety lockout defeat life-safety protection. Find the cause; never just reset the count.
Next steps
Fix the trigger condition first, then address any collateral damage the resets created. Verify by running the system through a full cycle and confirming the protection does not trip.
Explain to the customer, plainly, that the lockout was the equipment protecting itself and that repeated resets risked turning a controlled fault into a destroyed component or a hazard. This reframes the lockout as a feature, which it is, and discourages the next reset loop.
Document the as-found fault code and reset count. It is the record that the failure was real and recurring, not a nuisance you cleared.
References
- ISO 13379-1, Condition monitoring and diagnostics of machines, interpreting protective trips as diagnostic signals.
- NFPA 70, National Electrical Code, ground-fault and overcurrent protective device function.
- OSHA 29 CFR 1910, General Industry standards on not defeating equipment safety controls.
- NFPA 54, National Fuel Gas Code, ignition-system flame-safety lockout function.