Scan data

Permanent Trouble Code Won’t Clear: What to Check After a Repair

A permanent code can remain after a repair. Learn what the vehicle must verify, what evidence to save, and when to ask for further diagnosis.

Permanent does not mean unrepairable

You repaired the fault, the check-engine light is off, but the scanner still lists a permanent diagnostic trouble code. Before buying another part, check which code status you are reading.

A permanent code is not something an erase button is meant to remove. The vehicle’s diagnostic system must verify that the relevant problem is gone. Disconnecting the battery is not a shortcut. California’s Bureau of Automotive Repair explains this distinction in its permanent-code overview.

That does not automatically mean the repair succeeded, either. The next step is to compare the remaining code with current symptoms, the warning-light status and the results of the vehicle’s self-tests.

Read the report, not just the code number

Save the complete scan report. Record the exact heading above each code, the module reporting it and whether the scanner says the malfunction indicator lamp is commanded on or off. A cropped screenshot showing only “P0420” leaves out information needed to interpret the result.

Scanner labels vary. A permanent emissions-code list should not be treated as interchangeable with a manufacturer’s “history,” “current” or other enhanced diagnostic category. Check the scanner’s documentation if the category is unclear. If the permanent-code function is unavailable or unsupported, record that limitation instead of writing “no permanent codes.” A successful ordinary-code read is a different result. The Autel AL519 manual, Read Codes section is one example of separate stored, pending and permanent selections with vehicle-support limits.

Use this worksheet when discussing the repair:

Record Why it helps the next decision
Exact code, module and status label Separates the remaining permanent entry from other reported faults.
Whether the light is on, off or flashing Gives the technician the current warning behaviour.
Symptoms before and after repair Shows whether the original complaint changed.
Work performed and tests used to justify it Helps distinguish a diagnosed repair from a parts guess.
Readiness status and any recent code clearing Gives context for the available self-test results.

A permanent-code entry alone is not a reason to repeat an expensive replacement. Equally, do not dismiss renewed shaking, stalling or a returning warning because someone described the code as “old.” If the light flashes or the engine runs badly, use the warning-light guide before planning more driving.

Give the correct monitor a chance to verify the repair

BAR explains that the underlying defect must be repaired and the monitor that identified it must run again successfully before the permanent code clears. The relevant event is a completed diagnostic check, not simply another press of the erase button. BAR permanent-code overview.

Ask the technician which monitor is relevant and what the manufacturer requires for that vehicle. Do not substitute a generic internet driving routine. Avoid a suggested procedure that conflicts with traffic conditions or the vehicle’s operating instructions.

For a persistent code, ask for a focused explanation: “Has the relevant test run since the repair, and what result did it report?” That is more useful than requesting an arbitrary number of kilometres or asking whether the scanner can force the code away. Use the manufacturer’s complete clearing criteria rather than promising that one successful restart will remove every permanent entry. Record what the relevant monitor has actually evaluated; a general “ready” label is not a substitute for that explanation.

Stop erasing the evidence

Repeatedly clearing diagnostic memory can remove useful fault information and reset readiness. EPA guidance specifically identifies codes and associated freeze-frame data as important diagnostic evidence before repair. EPA OBD inspection guidance.

Keep the original report and a dated follow-up report. If a technician needs to clear ordinary codes as part of a diagnostic procedure, ask them to preserve the information first. Our freeze-frame guide explains what that saved snapshot can contribute.

An empty ordinary-code list immediately after erasing memory is not proof that the original fault has been corrected. A better repair record explains the initial finding, the test that justified the work and the checks performed afterward.

If it still will not clear

Return with the reports rather than replacing another component based only on the remaining number. Ask whether the original fault is recurring, the relevant test has not completed, or a vehicle-specific issue needs investigation.

BAR’s OBD test reference lists vehicles with known permanent-code clearing difficulties, including some addressed by manufacturer campaigns or software updates. The useful next step is to check applicability to the exact vehicle; the existence of such a list does not prove that your vehicle needs reprogramming.

For a converter-related code, the P0420 diagnostic guide provides context for discussing the underlying fault. For an evaporative-emissions code, use the EVAP guide. Neither is a substitute for the manufacturer’s procedure.

Does a permanent code affect an inspection?

Inspection requirements depend on location and vehicle applicability. California BAR includes permanent codes in its OBD inspection criteria and describes exceptions in its current test reference. Those California rules are not a universal driving prescription or an Ontario inspection rule.

If an inspection deadline is approaching, ask the relevant inspection provider what applies to your vehicle before spending time on a drive cycle. Keep the repair invoice and before-and-after reports available. Do not assume that a dark check-engine light guarantees an inspection pass.

This is general education, not a vehicle-specific repair procedure or hands-on test. Read the editorial policy.

Search this site's starter library by trouble code, symptom or topic. This is a guide search, not an automated vehicle diagnosis.