Pending Confirmed And Permanent Obd Codes Explained
Pending, confirmed (often shown as stored) and permanent are distinct OBD diagnostic trouble code (DTC) status labels. Each status describes how the vehicle’s OBD system is classifying a monitored condition. None of them, on their own, proves which part has failed, that a repair is complete, or that the vehicle will pass an MOT.
Pending, stored or confirmed, and permanent compared
| Status | What it can indicate | What it cannot prove |
|---|---|---|
| Pending | A monitor has recorded a potential or intermittent condition that may mature into a stored fault if the required enabling criteria repeat. | That the issue is harmless, finished, or that any named component must be replaced. |
| Stored / confirmed | The module has retained a fault that met its criteria for storage and may relate to warning-lamp behaviour. | Exactly which component failed, or that clearing the code repairs the cause. |
| Permanent | An emissions-related fault record that ordinary scan-tool clear or battery disconnection does not erase; the OBD system clears it after it verifies the malfunction is no longer present. | That you can wipe it with a quick clear, or that the fault is necessarily active at this exact second. |
Exact on-tool wording varies by vehicle and software. Keep the label your reader shows, even when everyday UK English prefers “stored” over “confirmed”.
Why a pending code records an event without proving a failed part
A pending code is diagnostic evidence of a detected condition that has not necessarily completed every confirm cycle. It can matter when symptoms are already present, and it can disappear if the condition does not repeat under the module’s rules. It still does not identify a guaranteed failed sensor, actuator or other part.
- Record the pending text, date, mileage and what you were doing when the symptom or lamp appeared.
- Do not dismiss pending as “nothing” without checking the vehicle handbook and the symptom timeline.
- Do not order parts from a pending description alone.
How a confirmed or stored code relates to the warning lamp
A stored or confirmed emissions-related code may illuminate the engine management lamp, but lamp state and code status are related records, not interchangeable fields. The lamp can be off while information still exists in the module, or on while you are still gathering freeze-frame and live context. UK roadside guidance treats the engine management lamp as a reason for professional checking, not as a named-parts verdict, and treats a red or flashing lamp or serious accompanying symptoms as a stop-and-seek-help situation.
Use code status together with lamp behaviour, freeze frame where available, and the driver’s symptom notes. That combination forms the start of diagnosis; it does not finish it.
Why an ordinary clear or battery disconnection does not erase a permanent DTC
Official permanent-DTC guidance explains that permanent codes cannot be removed by battery disconnection or an ordinary scan-tool clear. The OBD system clears them after it verifies the original malfunction is no longer present. Tool manuals also note that clearing erases temporary ECU information such as freeze frame but does not repair the underlying cause, and that available options vary by year, make and model.
- Record codes, status labels and freeze frame before anyone clears temporary information.
- Correct the cause using manufacturer procedures or a competent workshop.
- Expect permanent records to remain until the vehicle’s own monitors verify the repair.
- Do not treat disappearance of a temporary code as proof the fault is gone if a permanent record or symptoms remain.
Record-before-clear checklist and vehicle-specific terminology
Before changing anything:
- Photograph or write the exact code string, status word and lamp state.
- Save freeze-frame fields exactly as displayed, including units and blank or N/A entries.
- Note mileage, date and a short symptom sentence in the driver’s words.
- Preserve manufacturer-specific wording instead of forcing every label into a generic glossary.
Stop DIY interpretation and escalate when a red or flashing warning lamp is present, when drivability or safety is affected, when electrical or emissions testing beyond a basic scan is required, or when tool menus conflict with the vehicle handbook.
Next step and FAQ
If you want a wired handheld that can read and distinguish supported OBD code statuses when the vehicle provides them, review the Foxwell NT301 OBD2 scanner details on DIY Fault, then confirm functions for your exact vehicle in the product and tool manuals. A 12-month warranty duration is the only warranty period stated for products sold via this independent store here. For related context, see the freeze frame data checklist before clearing a code and the engine management light UK guide.
Is a pending code safe to ignore?
No. Pending means a monitor flagged a potential or intermittent condition. Record it and compare it with symptoms rather than assuming it is harmless.
Can I erase a permanent DTC by disconnecting the battery?
No. Permanent DTCs are not removed by battery disconnection or an ordinary clear; the OBD system clears them after verification.
Does a confirmed code tell me which part to buy?
No. Confirmed or stored status means the module retained a fault meeting its criteria. Inspect and test before replacing parts.
Will clearing codes prove the car will pass an MOT?
No. Clearing removes temporary diagnostic information and does not repair the cause or decide an MOT result.