The phrase “there was a code” is often too vague to compare repair visits. Pending, stored or confirmed, and permanent codes can describe different stages in the OBD-II process, and California BAR treats permanent diagnostic trouble codes differently from ordinary codes in Smog Check testing.
Record the code state, not only the number
A pending code generally means the monitor detected a condition but has not yet met the criteria for a confirmed fault. A stored or confirmed code reflects that the system’s criteria were met. For vehicles that support them, a permanent code cannot simply be erased with a scan tool or battery disconnect; the OBD-II system clears it after the relevant monitor verifies the defect is no longer present.
These labels are diagnostic context, not legal conclusions. Their value comes from connecting them to a date, mileage, warning status, freeze-frame conditions, repair action, and later monitor result.
- Exact alphanumeric code and whether it was pending, confirmed, or permanent.
- MIL command status and whether the light was visible to the driver.
- Freeze-frame or failure-record data when available.
- Readiness-monitor status before and after repairs or battery disconnection.
Why clearing data can complicate the chronology
Clearing ordinary codes may remove useful diagnostic context and reset readiness monitors. BAR explains that monitors must run again after events such as a battery disconnect or emissions-component repair. A clean scan immediately after clearing is therefore not the same as a completed monitor confirming a repair.
If a dealer clears data as part of legitimate service, the repair order should still preserve the codes found, tests performed, and correction attempted. That written history lets a later reviewer distinguish a resolved fault from a reset followed by recurrence.
A record-first next step
Ask for the scan report or request that the service adviser write the code state and readiness status into the final repair order. Use the topic-specific evidence toolkit to organize the chronology, compare it with the site guide library, and review the primary-source notes. A question about an individual vehicle requires a case-specific review; the case-review page is the appropriate starting point.
Primary sources
- California BAR On-Board Diagnostic Test Reference
- California BAR Smog Check requirements
- California Civil Code section 1793.2
Attorney Advertising. This educational article is not legal advice. A diagnostic code, repair count, symptom, recall, or days-out-of-service figure does not by itself establish a claim. Laws, procedures, records, warranties, and facts vary. No result is promised or guaranteed, and submitting a form does not create an attorney-client relationship.
How to make this record case-specific
Apply this guide to the actual vehicle rather than a general online pattern. For each occurrence, record the date, mileage, operating conditions, exact warning or symptom, and whether the vehicle could be driven safely. A phrase such as pending, confirmed, or permanent diagnostic codes should be tied to what the driver observed and what the repair order says. Do not treat a code, warning, forum report, recall, or service bulletin as a confirmed diagnosis unless the vehicle-specific repair file supports that conclusion.
Then compare the complaint, cause, and correction lines across visits. Look for recorded testing or work involving wiring, connectors, and software calibrations, along with part numbers, software versions, road-test notes, and cannot-duplicate language. Preserve warning photographs with date and mileage with the warranty booklet, purchase or lease documents, dealer communications, photographs, towing or rental records, and a calculation of the days the vehicle was unavailable. These details help an attorney distinguish repeated observations from repeated repair attempts and evaluate the history under the current warranty and California law.
Before requesting a review, check that each final repair order uses accurate complaint language and dates. Keep later messages showing that the condition returned. The purpose is not to force the facts into a preset rule; it is to create a reliable chronology for the individual vehicle. Continue through the defect evidence hubs and manufacturer document hubs for the record paths applicable to persistent check-engine lights and onboard diagnostic faults.