Free Delivery on orders over $49.9. Don’t miss discount.
Blog

Pending vs Confirmed vs Permanent Diagnostic Trouble Codes

Illuminated check engine light on a generic car instrument cluster

A check engine light is only part of the story. The same scan tool that shows a catalyst or misfire code also sorts that fault into pending, confirmed, or permanent diagnostic trouble codes. Those three buckets are not interchangeable. If you treat a pending code like a finished diagnosis, you may replace a part that has not actually failed a monitor twice. If you ignore a permanent DTC after you “cleared the light,” you can still fail a smog inspection. Learning pending vs confirmed vs permanent DTCs keeps the diagnosis honest and tells you what a scan tool is actually allowed to erase.

Pending codes: a fault that has not fully matured

A pending diagnostic trouble code is a fault the computer has detected, but not yet confirmed. Many emissions monitors are two-trip tests. The first failed trip stores a pending code and usually leaves the malfunction indicator lamp (MIL) off. If the same test fails again on a later drive cycle, the code typically becomes confirmed and the light comes on. One-trip codes, such as some misfire or severe fuel-system faults, can illuminate the light sooner; their pending stage may be brief or easy to miss.

Pending codes matter because they are early evidence. A pending catalyst, EVAP, or oxygen-sensor code can explain a mild drivability complaint before the lamp is on. They also tell you a monitor has already failed once, so a short “it seems fine now” idle in the bay is not a complete test. Our guide on how to use freeze frame data applies here too: if a pending code has a frame, save it before anyone clears memory.

Do not treat a lone pending code as proof that a part is bad. It is a reason to inspect, record live data, and, when it is safe, repeat the conditions that set the fault. If the next trip passes, the pending code may disappear on its own. That is useful information, not a nuisance.

Confirmed or stored codes: the light’s usual partner

Technicians use several labels for the next stage. On generic OBD2, a confirmed or stored (sometimes called a memory) code is a diagnostic trouble code that has met the criteria to be saved and, for most emissions faults, to command the MIL on. This is the list a parts-store reader prints, and the list most drivers mean when they say they “have a code.”

“Current” or “active” on an enhanced or OEM screen is a slightly different idea. It usually means the fault is present during this key cycle, not only stored from last week. A confirmed code can remain in memory with the light on, then become a history code after a repair, a passed monitor, or a clear. Read the labels your tool actually uses, and record all three lists if it offers pending, stored, and permanent views.

A confirmed emissions code is the one you should diagnose with a process, not a guess. Capture the full code list, freeze frame, and relevant live data before you clear anything. If you want the basic workflow, start with how to read and clear a check engine light. Then use a code-specific path when you have one, such as P0420, P0171 and P0174 lean codes, EVAP leak codes, or engine misfires.

Permanent DTCs: the codes a scan tool cannot erase

Permanent diagnostic trouble codes are the ones shops and DIYers most often misunderstand. Since the 2010 model year, light-duty vehicles sold in the United States have stored permanent DTCs (generic OBD2 Mode $0A) when the MIL is commanded on for an emissions fault. A scan tool can display them, but it cannot clear them with the usual erase-codes command. Clearing stored and pending codes, disconnecting the battery, or even swapping a part will not immediately remove a permanent DTC.

The computer clears a permanent code only after it runs the required monitor — often the same test that failed — and the test passes. Until then, the permanent code remains as evidence that a fault recently commanded the light on. That is deliberate. It exists so a vehicle cannot be “cleaned up” for an inspection with a quick code clear in the parking lot.

This matters in smog states and in any state that reads OBD2 at inspection. A vehicle can have the MIL off, stored codes cleared, and still show a permanent DTC if the repair has not been verified by the monitor. If the car is headed for a test, read how OBD2 readiness monitors work and complete the drive cycle instead of repeatedly clearing memory. A permanent code that remains after a repair is not a tool failure. It is the computer telling you the monitor has not passed yet.

How to read all three lists on a typical scan tool

A basic code reader such as the Autel MaxiScan MS309 will usually show stored and pending emissions codes and freeze frame. Many mid-level tools and a Bluetooth unit such as TopScan also make the permanent-code list easier to find and save. The menu names vary: look for pending, stored or confirmed, and permanent or Mode $0A. Enhanced manufacturer codes in ABS, airbag, or body modules follow different rules and usually do not have generic permanent DTCs.

When you connect:

  • Record pending, stored, and permanent codes, not only the one on a printout.
  • Note which codes have a freeze frame, and whether the MIL is commanded on or off.
  • Save a screenshot or a written list before you clear anything.
  • After a repair, check the permanent list again. If the code is still there, finish the monitor, then recheck.

If a tool shows a stored code but no permanent code on a late-model car, that can be normal for a non-emissions module fault, a very recent set, or a tool that is not displaying Mode $0A. Confirm in another menu or with a second tool before you assume the computer never stored a permanent DTC.

What you can clear, and what you should not rush

You can typically clear pending and stored generic codes with a scan tool. That also wipes generic freeze frame and resets readiness monitors. It does not repair the vehicle, and it will not remove a permanent DTC. Clearing “to see if it comes back” is a common habit that costs you evidence and, in an inspection state, time.

A better sequence is to diagnose first, repair or verify as needed, then clear stored and pending codes only if you have recorded them and you understand the inspection consequences. Drive the vehicle so the relevant monitors can run. Watch the permanent code and the readiness status. If the permanent DTC remains and the monitor never completes, the fault may still be present, the drive cycle may be incomplete, or an enable condition such as fuel level, temperature, or speed is not being met.

Pending vs confirmed vs permanent DTCs are three views of the same diagnostic system. Use all three, leave the permanent list for the computer to clear, and let the monitors confirm the repair. That is how you avoid both a parts-cannon diagnosis and a failed retest.

Select your currency
Our customer support team is here to answer your questions. Ask us anything!