S Signal & Spanner
Diagnostic Logic

Pending vs Stored vs Permanent Trouble Codes

A Signal & Spanner guide · Updated 2026-07-19 · 4 min read
Pending vs Stored vs Permanent Trouble Codes
Quick answerA pending code generally records an initial detected condition that has not yet met the criteria to mature. A stored or confirmed code has met the monitor's application-specific logic, though it still does not prove which part caused the condition. A permanent emissions code remains until the OBD system verifies through its required monitoring that the repaired fault no longer exists; clearing commands are not a repair. Save every status, freeze-frame record, readiness state, symptom, and recent event before clearing, then diagnose and verify using exact vehicle service information.
Contents

Code status tells part of the timeline

Pending, stored or confirmed, and permanent diagnostic trouble codes describe different stages in OBD fault handling. Scan tools sometimes use slightly different labels, and manufacturer-enhanced modules may add history or current categories. Always read the exact tool and vehicle documentation before translating the screen.

Status is not severity. A pending code can involve a serious developing condition, while an old stored code may describe an intermittent event that is not occurring now.

A pending code is an early observation

A pending code generally means a monitor detected a fault condition but has not yet met the criteria to mature it and command the malfunction indicator. The system may need the condition to repeat, persist, or occur under particular operating criteria.

Record it before it disappears or matures. Compare symptoms, trip history, freeze-frame availability, test results, and whether other modules report related events. Do not clear it simply because the light is off.

A stored or confirmed code met its criteria

A stored code has satisfied the monitor logic defined for that application. It may command a warning light, depending on the code and current fault state. The code can remain after the condition stops so diagnosis has a trail to follow.

“Confirmed” confirms the monitor decision, not the component cause. Read the code without guessing and test the entire circuit or system.

A permanent code has special clearing logic

Permanent emissions-related codes are designed to remain available until the OBD system verifies through its required monitoring that the relevant fault is no longer present. A scan-tool clear command or battery disconnect is not the repair and generally should not be treated as a way to remove this status.

Complete the documented repair, then operate the vehicle only through safe, legal conditions specified by its service and inspection information. Do not invent a universal drive cycle or drive dangerously to force a monitor.

Freeze-frame and readiness add context

Freeze-frame information can preserve values from when a fault met storage criteria. A pending detection may have different or limited snapshots depending on the vehicle and tool.

Readiness monitors say whether applicable emissions self-tests have completed since a reset or relevant event. “Not ready” is not the same as “failed,” and “ready” does not mean every vehicle system is healthy. EPA guidance describes ready, not ready, and not applicable as monitor-evaluation states.

Do not diagnose by deletion

Before any clearing, save a complete scan report. Clearing can remove diagnostic context, reset readiness, and make an intermittent fault harder to reproduce. It also cannot repair a loose terminal, air leak, mechanical problem, or failed circuit.

If a seller, shop, or inspection record shows recently reset monitors, ask why and wait for proper evaluation rather than assuming a clean screen means a clean vehicle.

Verify each layer after repair

Confirm the symptom is gone, relevant data and tests pass, pending and stored codes behave as service information predicts, applicable monitors complete, and permanent status clears through the system's own verified logic. Local inspection rules differ, so use the current responsible authority rather than a universal readiness shortcut.

The scanner is a timeline, not a slot machine. Pulling the lever again does not improve the evidence.

Sources

FAQ

Can a pending code turn off by itself?

A pending status may disappear if the detection does not repeat under the monitor's criteria, or it may mature into a stored code. That does not make the original event imaginary. Record it with symptoms, operating conditions, and related codes, then use service information to decide whether inspection or controlled testing is required.

Can I erase a permanent trouble code with a scanner?

A standard clear command is not the intended way to remove a permanent emissions code. Correct the verified cause, then allow the OBD system to run the applicable monitor under the vehicle's documented safe conditions. The code clears when the system confirms the fault is resolved. Local inspection treatment varies, so check current authority guidance.

Does a stored code mean the problem is happening now?

Not necessarily. It means the detection criteria were met and the evidence was stored. The condition may be current, intermittent, or no longer active. Compare warning status, current and historical scan data, freeze-frame values, symptoms, circuit tests, and service logic. Never replace a part solely because its name appears in the code description.