A check-engine light that comes back after a dealer clears it or performs a repair can represent an unresolved condition, a new condition, or an incomplete diagnostic path. The warning alone does not establish which explanation is correct; the repair chronology does.
Separate the warning from the underlying defect
The malfunction indicator lamp is the vehicle’s alert that its on-board diagnostic system detected an emissions-related fault. A diagnostic trouble code points technicians toward a system or test result; it is not always a final parts diagnosis. The most useful file pairs the code with the driver’s symptoms, freeze-frame data, technician testing, repair performed, and what happened afterward.
When the light returns, compare whether the same code family, symptom, or operating condition appears again. A new code may still relate to the same unsuccessful repair, but that conclusion should come from the records and diagnosis rather than an assumption.
- Photograph the warning and odometer when safe to do so.
- Ask that every reported symptom and code be written on the repair order.
- Keep the before-and-after diagnostic printouts if the facility provides them.
- Record how long the light stayed off after each repair.
Why repeat repair history matters
California Civil Code section 1793.2 addresses a manufacturer’s duty to service or repair goods covered by an applicable express warranty and provides possible replacement or restitution remedies after a reasonable number of attempts. What is reasonable is fact dependent. Section 1793.22 contains a rebuttable presumption for specified circumstances, not a universal checklist that decides every matter.
A useful review therefore looks beyond the count of visits. It asks whether the warranty applied, whether the complaints describe the same nonconformity, whether the facility had a fair opportunity to diagnose it, how the condition affected use, value, or safety, and how many days the vehicle was unavailable.
A record-first next step
Build one row for each repair visit and include the code, complaint language, mileage in and out, diagnosis, repair, and date the warning returned. 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 Civil Code section 1793.2
- California Civil Code section 1793.22
- California DCA Arbitration Certification Program
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 steady or flashing malfunction indicator light 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 ignition, fuel, air, and control modules, along with part numbers, software versions, road-test notes, and cannot-duplicate language. Preserve repair orders and post-repair verification 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.