How stored, pending, and permanent code states differ, and why a scan tool cannot simply erase every emissions record.
Three code states carry different evidence
Stored codes represent confirmed qualifying faults in controller memory. Pending codes can reflect a fault observed before the confirmation threshold. Permanent codes are designed to remain until the vehicle confirms through its own monitoring logic that the relevant condition is no longer present.
Clearing changes the evidence environment
A clear can reset freeze-frame context and readiness monitors. That can delay inspection readiness and make a recently reset vehicle appear quiet before its self-tests complete.
- Capture all code states before clearing.
- Record freeze frame and readiness first.
- Repair the measured cause rather than the code label.
- Repeat the proving condition and allow the monitor to run.
Verification belongs to the vehicle logic
A responsible after-repair record compares the original fault status, operating condition, live evidence, monitor result, and recurrence window. The absence of an immediate warning light is useful but incomplete.
THE TAKEAWAYA permanent DTC is cleared by successful monitor evidence, not by a stronger erase button.
ScanWrench Editorial created this issue from the platform's evidence model and reviewed educational workflows. It separates observed facts, plausible paths, decisive tests, safety limits, and remaining unknowns. Its purpose is to improve vehicle decisions; it does not replace exact manufacturer procedures or qualified professional judgment.
See how this page earns trust.
These links are primary-source starting points for the page's scope. They do not replace the current manufacturer procedure, wiring, specification, or service information for a specific vehicle.
Publisher
ScanWrench Editorial is the working byline for this library. Joshua Black, founder and publisher, is responsible for publication decisions, disclosures, and corrections.
A reviewed date means an editorial scope and safety check. It is not an ASE credential, OEM authorization, or vehicle-specific repair approval.
Primary sources
- Vehicle safety recallsNational Highway Traffic Safety Administration · Official VIN-level U.S. safety-recall lookup and recall guidance.
- NHTSA datasets and APIsNational Highway Traffic Safety Administration · Primary U.S. recall, complaint, investigation, rating, and manufacturer-communication data.
- On-Board Diagnostic Test ReferenceCalifornia Bureau of Automotive Repair · Official readiness, permanent-code, communication, and inspection-test context for California.
Revision history
- Initial publication and review: claim boundaries, safety language, internal links, and cited source scope checked.
No material correction has been recorded after this edition. If that changes, the correction and review date will be listed here.
Report a possible correction ↗