Home  /  Guides  /  Permanent OBD code after repair: check status before replacing parts

Technician reference

Permanent OBD code after repair: check status before replacing parts

A permanent OBD code remains after repair? Separate retained codes from returning faults, check monitor evidence and avoid repeated clearing or unnecessary parts.

Bring your vehicle details, symptoms and fault codes into a diagnostic conversation.

Download MechNostic on the App StoreGet MechNostic on Google Play
Published Updated interpret a retained permanent OBD diagnostic trouble code after repair without treating it as proof of a current component failure

Applicability & limits

BAR sources describe US/California OBD behaviour and inspection policy. Bosch describes its OBD 1300 scan tool, not universal scanner coverage. This guide gives no UK MOT or other inspection-pass prediction, roadworthiness decision, universal drive cycle, clearing deadline or confirmed repair diagnosis.

Vehicles
Vehicles confirmed to support permanent emissions-related OBD diagnostic trouble codes
Engines
No engine-specific diagnosis, test value or repair procedure is supplied
Model years
Support must be confirmed for the exact vehicle; model year alone is insufficient. No universal year range is claimed.
Markets
United States: California source context, Other markets: explanatory use only with confirmed permanent-DTC support

01

A permanent code alone does not condemn the replacement part

A permanent emissions-related DTC cannot be erased with a scan-tool clear command or by disconnecting the battery. California's Bureau of Automotive Repair explains that the vehicle clears it after the underlying problem is repaired and the relevant monitor verifies that the fault is absent.[bar-explanation]

The workshop implication is limited but useful: a permanent code remaining after a reported repair does not, by itself, prove that the replacement part has failed. Equally, a lamp that is now off does not prove that post-repair verification is complete.[bar-explanation]

02

First establish exactly what the scanner is reporting

Save the complete DTC, its displayed status and the reporting module. Check whether the same code is also reported as pending or current, and record the lamp status and available monitor information. Do not reduce several status fields to one note saying code still there.[bosch][evidence]

Record the confirmed vehicle details, repair performed and any subsequent erase or battery-disconnection event. If the scanner cannot show a relevant field, mark it unavailable. Bosch's manual distinguishes DTC types and monitor views; availability varies. These recording steps are editorial guidance.[bosch][evidence]

03

Choose the next branch from the evidence

If the complaint recurs or the code returns as a current or pending fault after the repair, investigate it using the exact vehicle's manufacturer procedure. Do not dismiss that evidence as merely an old permanent entry.[bar-current][bosch]

If only the permanent entry remains, establish whether the relevant monitor and its required conditions have been checked. BAR notes that monitor completion depends on operating conditions and functioning components. Lack of completion can reflect missing conditions or an unresolved enabling fault; it is not a reason to promise clearance after a fixed mileage.[bar-current][bosch]

If verification appears complete but the entry persists, confirm the correct code, monitor and vehicle information before choosing another repair. BAR identifies vehicle-specific clearing problems and manufacturer campaigns. Check exact applicability; a listed issue on another model is not a diagnosis.[bar-current][bosch]

04

Repeated clearing can remove useful evidence

Bosch warns that erasing codes resets readiness and can remove freeze-frame or monitor-test information, depending on the vehicle. It cannot erase permanent DTCs. Preserve the starting scan and follow the applicable procedure before making another change.[bosch][evidence]

Use the related evidence-capture guide to prepare the record. Do not substitute an improvised road drive for the manufacturer's verification conditions.[bosch][evidence]

05

Inspection treatment is a separate question

California inspection exceptions do not mean the vehicle has erased a code or that a repair is proven. They also do not establish a UK MOT or other jurisdiction's result. Use current local requirements for inspection decisions.[bar-current]

06

Bring the evidence into MechNostic

Enter the confirmed vehicle details, exact DTC and status, repair history and monitor findings, or add clear photographs of the scanner displays. MechNostic supports text and photo inputs; verify any extracted text against the original.[mechnostic]

Try this prompt: Separate the observed code statuses from assumptions about repair success. What evidence is missing to choose the next diagnostic check, and what manufacturer information should I verify?[mechnostic]

Use the response alongside your measurements and current service information. MechNostic cannot establish that a monitor has run or a repair has succeeded without supporting evidence.[mechnostic]

Reference desk

Sources

Consult the original material and confirm it applies to the vehicle in front of you.

  1. [bar-explanation]California BAR: Permanent Diagnostic Trouble Codes, Spring 2019

    Supports: Explains permanent-DTC retention and vehicle-controlled clearing after repair and monitor verification. Historical explanation; current inspection rules are checked separately. Not an OEM procedure or universal market-coverage statement.

  2. [bar-current]California BAR: On-Board Diagnostic Test Reference, revision history through 8.6

    Supports: Sections B/C/E: latest displayed revision is 8.6, 5 March 2026; readiness conditions, permanent-DTC rules and vehicle-specific clearing issues/campaigns. Supports bounded interpretation, not a generic drive cycle, UK MOT rules or a failed-part diagnosis.

  3. [bosch]Bosch OBD 1300 User Manual, 573700 Rev B, March 2016, sections 5.1–5.3

    Supports: Pages 27–30 distinguish monitor views, module identity and DTC type, describe support limitations and warn that erase resets readiness and may remove other evidence. Tool-manufacturer reference only; no promise of compatibility or identical behaviour for every vehicle.

  4. [evidence]MechNostic: Capture diagnostic evidence before clearing a fault code

    Supports: Related practical pre-clear recording workflow; editorial guidance, not manufacturer repair authority.

  5. [mechnostic]MechNostic product information

    Supports: Publicly described vehicle, symptom, code and scanner-photo inputs. Does not substantiate diagnostic accuracy, universal device coverage or a guaranteed repair.

Take MechNostic with you.

Get the app on iPhone or Android. Use diagnostic references alongside current manufacturer information and appropriate test procedures.

Download MechNostic on the App StoreGet MechNostic on Google Play