Pending vs Stored vs Permanent OBD2 Codes: What Your Scanner Actually Shows
In this guide
Seeing the same P-code under multiple headings can make a scan report look contradictory. In reality, a scanner may be showing different states of diagnostic detection. A pending code, a confirmed/stored diagnostic trouble code and a permanent code do not carry identical meanings, and the ability to erase a code from one view does not prove the vehicle is repaired.
Quick answer: Record the complete code status and associated freeze-frame information before clearing anything. A pending code can signal a monitored fault that has not met the conditions for a confirmed fault; a confirmed/stored code has satisfied its diagnostic criteria; a permanent code is intended to remain until the vehicle’s onboard system confirms that the fault is no longer present. Actual details vary by vehicle and by regulation.
A practical side-by-side explanation
| Status | What it generally indicates | What buyers should not assume |
|---|---|---|
| Pending | A fault monitor detected a condition that may need further confirmation | That the fault is imaginary or safe to ignore |
| Confirmed/stored | A diagnostic trouble code satisfied storage criteria | That replacing the named part will cure it |
| Permanent | OBD retains a particular verified emissions-related fault state until onboard verification | That a scan tool can simply erase it |
The California Bureau of Automotive Repair’s OBD reference explains that permanent DTCs cannot be erased by clearing ordinary codes or disconnecting the battery; the vehicle’s system must determine that the identified fault is no longer present. State inspection treatment is regulatory and may change, so do not use old inspection advice as current legal guidance without checking the jurisdiction.
Pending doesn’t mean harmless
An intermittent misfire, sensor wiring issue or fuel-system condition may appear initially as pending under some circumstances. The status depends on diagnostic logic: the controller may require repeated conditions before a confirmed code or malfunction-indicator response. The right next step is not automatically to erase it. Preserve the code number, status, relevant monitor data and operating conditions before deciding what needs professional inspection.
A pending code can disappear after later tests pass, or become confirmed if the fault recurs. That is why a single scan screenshot is weak evidence about an intermittent problem. If the dashboard warning flashes, the vehicle runs badly or a safety system reports a fault, follow the manufacturer’s immediate safety advice rather than using a guide to diagnose while driving.
Why a stored code isn’t a repair diagnosis
A code identifies a detected condition or circuit, not necessarily a defective replaceable component. For instance, a sensor-related code might reflect a wiring, supply-voltage or mechanical condition rather than the sensor itself. Diagnostic reasoning uses service information, related codes, live data, freeze-frame records and repeatable observations.
A buyer who only wants check-engine codes may not need a professional tablet. A buyer investigating body, ABS or transmission modules needs a scanner with confirmed access to those controllers. Our Bluetooth adapter comparison helps distinguish those purchases.
Why permanent codes remain after clearing
The word permanent causes understandable frustration. In applicable OBD programs, the code reflects a stricter verification condition; it is not necessarily evidence of a repair currently failing, and it is not made to disappear by disconnecting the battery. The BAR reference describes vehicle-controlled clearing after successful onboard verification. Do not recommend repeated battery disconnections or unsafe “drive cycle hacks” to bypass emissions requirements.
A proper repair and relevant monitor completion can be important, but drive-cycle details must come from the vehicle maker and the local inspection authority. The purpose of code reading is to understand repair status, not to conceal faults ahead of an inspection.
What a good scanner should show
Look for the full code, status, module/source, freeze-frame values when available, and readiness monitor states. The richer the information, the easier it is to separate an intermittent condition from a stale record. A scanner listing “permanent codes supported” should still be verified against the vehicle’s actual OBD protocol and software. Generic OBD2 code status is not equivalent to full manufacturer-specific module history.
Record the scan date, VIN or vehicle identifier, odometer, warning-lamp state, module name and whether the repair occurred before the scan. Retain the original report before any code-clear attempt. If the same code returns, compare conditions rather than making assumptions from the code number alone.
When a tool exposes monitor-test results as well as codes, our Mode 6 versus live data guide explains why identifiers, units and limits are needed to interpret that additional evidence.
A diagnostic record can contain all three states
Imagine a car with an intermittent emissions fault. A scan may capture a pending code, while the same code family appears in stored history and a permanent emissions record under applicable rules. Those entries do not mean that three different parts have failed. The states describe different controller memory and verification conditions. The correct diagnosis depends on the service procedure and what operating conditions triggered the fault.
Before comparing two scanners, check whether their reports show code status clearly. A cheap device that displays only a short P-code list may be enough to begin investigating a warning light but may omit useful status and freeze-frame context. A more capable scanner is valuable only if it actually captures the needed information on your vehicle. Use our scan-report checklist to see what is worth retaining.
Code clearing and emissions readiness are not the same
Clearing ordinary codes can also reset readiness monitoring. That means a dashboard with no illuminated check-engine light may still show incomplete emissions monitors. The vehicle’s self-tests need to complete under appropriate conditions, and current inspection requirements vary by location. See OBD2 readiness monitors before inspection for the separate readiness question. Do not attempt to manipulate or conceal faults to pass a legal inspection.
What to do when buying a used vehicle
A recent code-clear event can make a vehicle’s electronic record harder to interpret. It may reset readiness monitors, and a scanner might not show the same history after the clear. That does not establish dishonesty or a hidden defect on its own, but it is a reason to request service records and an independent mechanical inspection rather than trust a “no codes” statement. A permanent code or incomplete readiness status should be assessed in the context of the vehicle and applicable emissions requirements.
If you are evaluating a used car, use the used-car scanner guide and remember that an electronic scan cannot certify brakes, body condition or mechanical wear. Avoid any claim that a code reader alone establishes that a vehicle is safe to purchase.
FAQs
Can a scanner erase a permanent code?
The California BAR reference says permanent diagnostic trouble codes are cleared by the vehicle’s OBD system after it verifies that the underlying condition is resolved, not simply by code erasure.
Does a pending code mean the car will fail inspection?
Not necessarily. Inspection rules vary by location, vehicle and the actual emission readiness/fault status. Refer to the relevant authority, not a generic online claim.
Why did a warning light return after I cleared a code?
Because clearing the memory does not cure an underlying condition. A later self-test can detect the issue again. Keep diagnostic records instead of repeatedly clearing the warning.
Final recommendation
Buy a scanner that can record context and code status, not merely display and erase P-codes. If the suspected issue involves a particular non-engine module, verify that coverage separately. Treat permanent codes as a repair-verification matter rather than something a supposedly better gadget can make disappear.
