Last Updated on October 18, 2026
Does that mean the car has three separate problems?
Usually, no. The code number identifies the system or condition in which the computer detected a fault. The status describes where that fault currently sits in the diagnostic process.
In other words, the code may remain the same while its status changes.
Understanding pending vs stored vs permanent codes helps you determine whether a fault has just appeared, has been confirmed, or is waiting for the vehicle to verify a repair.
It can also prevent unnecessary parts replacement and repeated attempts to clear a code that cannot yet be erased.
Quick Answer: Pending vs Stored vs Permanent Codes
A pending code means the onboard diagnostic system detected a possible fault, but the problem may not have met the conditions required for full confirmation.
A stored or confirmed code means the fault has met the applicable confirmation criteria and has been recorded in the control module’s diagnostic memory.
A permanent code is a protected record of a qualifying emissions-related fault. It cannot be manually erased with a standard scan tool or battery disconnection. The vehicle’s onboard diagnostic system must verify that the underlying problem is no longer present before removing it.
Remember: Pending, stored, and permanent describe diagnostic status. They do not automatically mean that three different components have failed.
The Code Status Journey
Imagine the vehicle’s computer as an inspector that continually tests emissions-related components and systems.
It does not necessarily turn on the check engine light the moment it notices one unusual reading.
A common diagnostic sequence looks like this:
Fault detected → Pending code → Fault confirmed → Stored code and possible warning light → Repair completed → Monitor passes → Relevant code status clears
Not every fault follows this exact sequence.
Some serious or one-trip faults can be confirmed during the first qualifying test. Others require the same problem to occur during another qualifying trip before the Malfunction Indicator Light (MIL) is commanded on.
A qualifying confirmed emissions fault may also create a permanent record.
The exact process depends on the fault, diagnostic monitor, vehicle manufacturer, and applicable OBD requirements.
What Is a Pending Code?
A pending code is an early diagnostic warning.
It means a monitor tested a system and detected a result outside its expected limits, but the computer may need additional evidence before declaring a confirmed malfunction.
For many two-trip emissions faults, the first failed test creates a pending DTC.
If the same monitor fails again during a later qualifying trip, the code may become confirmed or stored, and the check engine light may turn on.
If the monitor runs again and the problem does not return, the pending code may disappear automatically according to the vehicle’s diagnostic strategy.
However, clearing behavior varies. Certain misfire and fuel-system faults may receive more urgent treatment because they can affect emissions or catalytic-converter operation.
A pending code does not always mean a component needs replacement.
It may result from an intermittent electrical connection, an operating condition that occurs only occasionally, or an early-stage fault.
Still, it should not be ignored.
Record the code, note any symptoms, and check whether the problem returns when the relevant monitor runs again.
If the same pending code repeatedly appears, it provides stronger evidence of a recurring problem.
What Is a Stored or Confirmed Code?
A stored code generally means the control module has confirmed the fault and saved the DTC in memory.
For standardized emissions diagnostics, confirmed codes are commonly retrieved through OBD Mode $03, while pending codes are retrieved through Mode $07.
A confirmed stored code often accompanies an illuminated check engine light, but the relationship is not always that simple.
The light may turn off after the malfunction stops occurring, while a code remains available in memory.
Scanner terminology adds another layer of confusion.
One tool may call a code “stored,” another may display “confirmed,” and an enhanced scanner may separate current, history, and previously active faults.
Those terms are not always interchangeable across vehicle modules and scan-tool software.
Always check the exact status label, warning-light condition, available freeze-frame information, and vehicle-specific service instructions together.
Most ordinary stored emissions codes can be cleared using a compatible scanner after the repair.
However, clearing a code does not repair the vehicle. If the underlying condition remains, the monitor can detect it again and store another fault.
This is the practical foundation of pending vs stored vs permanent codes: pending usually represents an initial detection, while stored or confirmed means the diagnostic system has met the criteria to record a confirmed malfunction.
What Is a Permanent Code?
A permanent diagnostic trouble code, or PDTC, is a protected record of a qualifying emissions-related malfunction that has been confirmed by the vehicle’s onboard diagnostic system.
For conventional standardized OBD2 diagnostics, permanent codes are commonly retrieved through Mode $0A.
A permanent code does not necessarily mean the fault is still active.
It means the vehicle has not yet completed the required internal verification to remove the protected record.
For example, imagine that a catalyst-efficiency problem causes a confirmed P0420 code and turns on the check engine light.
After the underlying issue is repaired, a technician may clear the ordinary stored code with a scanner.
The light turns off, but P0420 may remain in the permanent-code section until the vehicle completes the required verification.
The California Bureau of Automotive Repair’s OBD test reference confirms that a permanent code cannot be manually erased by clearing ordinary DTCs or disconnecting the battery.
Only the onboard diagnostic system can remove the code after verifying that the previous malfunction is no longer present.
This protected memory helps prevent a temporary code reset from hiding an emissions problem immediately before an inspection.
However, it can also confuse owners who have completed a legitimate repair and expect every code to disappear immediately.
Not every stored DTC becomes permanent. Permanent-code support, qualifying faults, and verification requirements vary by vehicle.
There is no universal driving distance that guarantees a permanent DTC will disappear.
Pending vs Stored vs Permanent Codes: Direct Comparison
| Code Status | What It Usually Means | Check Engine Light | Manual Clearing | How It Disappears |
|---|---|---|---|---|
| Pending | A possible fault was detected but may need confirmation | Usually off for a pending-only fault | Generally possible | May disappear after passing tests or an appropriate reset |
| Stored / Confirmed | The fault met the confirmation requirements | Often on or previously on | Usually possible | Cleared through supported diagnostics or aged out under vehicle logic |
| Permanent | Protected record of a qualifying confirmed emissions fault | May be on or off | Not with a standard erase command | Removed by the vehicle after required verification |
These are general definitions, not a universal interpretation for every manufacturer-specific system.
Some scanners use “stored” for any fault held in memory, while others separate confirmed, current, history, and permanent records.
A code’s status should therefore be interpreted alongside readiness monitors, freeze-frame data, warning lights, and current symptoms.
Can the Same DTC Appear in Multiple Categories?
Yes. The same trouble code number can appear in pending, stored, and permanent sections because each category answers a different diagnostic question.
Suppose an emissions monitor detects a fault once. The code may first appear as pending.
If the monitor detects the problem again and the confirmation conditions are met, that same code can become stored or confirmed.
If the malfunction qualifies for permanent recording, a protected copy may also be retained.
Clearing an ordinary stored code does not erase the permanent record.
If the underlying problem remains, the monitor may detect it again and create another pending or confirmed entry.
Multiple listings do not automatically mean multiple failed components.
They may represent one problem at different diagnostic stages.
This is why comparing pending vs stored vs permanent codes should begin with the status rather than how many times the same code appears.
What If Only a Permanent Code Remains?
A permanent-only code with no current or pending version, an off check engine light, and no symptoms may indicate that the vehicle is still completing its repair-verification process.
That is different from a permanent code accompanied by a current or pending version of the same fault.
When current faults remain, additional diagnosis may be necessary before the responsible monitor can complete a successful test.
Do not keep clearing codes or disconnecting the battery in an attempt to remove a permanent record. Those actions cannot directly erase it and may restart other diagnostic checks.
What the Check Engine Light Can and Cannot Tell You
The check engine light is important, but it does not reveal every detail stored in the computer.
A pending-only emissions code usually does not illuminate the light because the fault may still require confirmation.
A confirmed code often commands the light on, although the warning may later turn off if the malfunction no longer occurs under the required conditions.
A permanent code does not automatically keep the light illuminated.
The light can be off while the vehicle waits for its onboard monitor to complete the necessary verification.
Therefore, “light off” and “no codes” are not the same result.
Likewise, a code remaining in memory does not always prove that the fault is active now.
If the check engine light is flashing, or the vehicle is severely misfiring, overheating, losing substantial power, producing heavy smoke, or smelling strongly of fuel, stop when safe and arrange professional assistance.
Those symptoms deserve more urgent attention than the code-status label alone.
How to Clear Pending vs Stored vs Permanent Codes
Before clearing any DTC, save the code number, status, freeze-frame information, and readiness-monitor results.
Erasing diagnostic information too early can remove valuable clues about when and why the problem occurred.
Clearing a Pending Code
A scanner can generally clear a pending code, but immediate clearing is not always helpful.
First, determine whether the fault was temporary or beginning to repeat.
If the monitor later passes according to the vehicle’s diagnostic logic, the pending code may disappear automatically.
If it returns or becomes confirmed, investigate the cause rather than repeatedly erasing it.
Clearing a Stored Code
Most ordinary stored or confirmed emissions codes can be cleared with a compatible scanner.
The warning light may turn off immediately, but the code can return if the underlying fault remains.
Clearing codes also commonly resets readiness monitors and may remove associated freeze-frame information.
Avoid disconnecting the battery as a shortcut. It may erase useful records and affect learned settings without correcting the original problem.
For a practical explanation of the erase function, read our guide to clearing OBD2 trouble codes after repairs.
Clearing a Permanent Code
A permanent DTC cannot be manually deleted with a standard scanner or battery disconnection.
Repair the original problem, confirm that the relevant fault is no longer active, and allow the responsible diagnostic monitor to run under the manufacturer’s required conditions.
There is no fixed number of miles or ignition cycles that clears every permanent code.
If the monitor appears to pass but the code remains, consult vehicle-specific service information and check for applicable technical service bulletins or software issues.
Important: Repeatedly pressing “Erase Codes” will not force a permanent DTC to disappear. The onboard diagnostic system must complete the required verification.
What Should You Do for Each Code Status?
If the Code Is Pending Only
Record the fault and watch for related symptoms. Investigate promptly if it returns, affects drivability, or involves a potentially damaging condition.
If the Code Is Stored or Confirmed
Diagnose the affected system before clearing the fault. A code identifies a detected condition, not necessarily the component that needs replacing.
If the Code Is Permanent Only
Check whether the original repair is complete and whether the associated diagnostic monitor has run successfully.
If the light is off and no pending or confirmed fault remains, the vehicle may still need to complete its automatic verification.
If All Three Statuses Appear
The original malfunction may still be present or may have returned. Compare the code statuses with current symptoms, monitor results, and diagnostic data before deciding what to repair.
Readiness Monitors and Emissions Testing
Clearing ordinary OBD2 codes commonly resets applicable readiness monitors to “not ready.”
These monitors represent self-tests performed by the vehicle’s emissions-control system.
A vehicle may therefore be rejected from an emissions inspection even when the check engine light is off.
Readiness status and permanent-code status are related but different. A monitor that is not ready does not automatically mean a permanent code is stored, and a permanent code may remain while other monitors are complete.
Inspection rules vary by location.
For example, California’s Smog Check program generally checks permanent codes on applicable 2010-and-newer vehicles that support them.
Under its specific inspection provision, a permanent code can be disregarded for that test when the vehicle has completed at least 15 warm-up cycles and 200 miles since OBD information was last cleared, subject to the program’s applicable conditions.
This does not mean the permanent code is physically erased after 200 miles. It is an inspection exception, not a universal code-clearing procedure.
Other states and testing programs may use different requirements. Check the applicable emissions-inspection rules before scheduling a test.
Why a Permanent Code May Take Longer to Disappear
A repaired vehicle still needs the right operating conditions for the relevant monitor to run.
For example, some emissions monitors require particular engine temperatures, fuel levels, driving conditions, or steady operation before testing can complete.
If those conditions have not occurred, the computer may not yet have the evidence needed to remove the permanent code.
Continually clearing ordinary faults can also reset readiness information and delay successful verification.
Rather than following a universal driving-distance recommendation, use the manufacturer-recommended procedure and avoid unsafe attempts to force a monitor to run.
Common Code-Clearing Mistakes
Several mistakes can make vehicle troubleshooting more difficult:
- Replacing a part solely because it appears in a code description.
- Clearing codes before saving freeze-frame information.
- Assuming every pending code is harmless.
- Believing an off check engine light means no faults remain.
- Trying to erase a permanent code repeatedly.
- Ignoring readiness monitors before an emissions inspection.
- Using one universal drive-cycle or mileage rule for every vehicle.
Freeze-frame information is particularly useful when a fault occurs only occasionally.
Our guide explaining what stored freeze-frame readings reveal can help you understand the operating conditions associated with a recorded fault.
Save the evidence first, identify the cause, and verify the repair before clearing diagnostic information.
Frequently Asked Questions
Is a Pending Code Serious?
Sometimes. A pending code may reflect an intermittent or developing fault. A returning code, flashing check engine light, or noticeable drivability problem deserves prompt investigation.
Does a Stored Code Mean the Fault Is Still Active?
Not always. Depending on the scanner and control module, it may represent a confirmed current fault or a previously recorded problem. Check the exact status and current operating conditions.
Can One DTC Have All Three Statuses?
Yes. The same fault can be represented as pending, confirmed or stored, and permanent during different or overlapping stages of diagnosis.
Can a Permanent Code Remain After Repair?
Yes. It may remain after a successful repair until the onboard diagnostic system completes the required verification and removes the protected record.
Should I Clear Codes Before an Emissions Test?
Usually not without a valid diagnostic reason. Clearing ordinary codes resets readiness monitors and may make the vehicle unready for inspection. It also does not manually remove permanent codes.
Can a Trouble Code Tell Me Which Part to Replace?
No. A trouble code provides a diagnostic direction. Wiring, connectors, leaks, sensor readings, operating conditions, or other components may produce the same code.
Conclusion
The key to understanding pending vs stored vs permanent codes is separating the trouble code number from its diagnostic status.
Pending means a fault has been detected but may not yet be confirmed. Stored or confirmed means the applicable fault criteria have been met. Permanent means the vehicle still retains a protected emissions-fault record until the required verification is completed.
Save the diagnostic information, identify the root cause, and check readiness before clearing anything.
A scanner can erase certain records, but it cannot replace a proper diagnosis or force a permanent code to disappear before the onboard system completes its checks.