Why Does the Check Engine Light Turn On and Off? What the Code Is Doing

The computer logs a fault the first time it sees one, but usually doesn't illuminate the light yet. If the same fault repeats under similar conditions, it confirms the code and the light comes on. If the fault then stops recurring for several drive cycles, the computer turns the light back off — without the underlying problem necessarily being fixed.

An intermittent light means an intermittent fault. The problem is real, it just isn't happening every time you drive.

This is the part almost nobody explains, and it's the whole mechanism.

The on-off pattern you're describing usually means you're bouncing between pending and confirmed.

For a steady, intermittent light:

• The gas cap. Genuinely the first thing to check, and not a joke. The evaporative emissions system pressure-tests the fuel system, and a cap that isn't seated or has a worn seal creates exactly the kind of come-and-go leak code that produces an intermittent light. Remove it, check the rubber seal for cracks, reseat it until it clicks.
• Recent fueling. If the light tends to appear shortly after you fill up, that points at the EVAP system too — overfilling past the first click can flood the charcoal canister.
• Weather correlation. Intermittent faults that track with cold mornings or humid days often point to a sensor operating near the edge of its tolerance, or a connector with moisture intrusion.

This is the most common misreading. A large share of emissions-related codes produce no symptom the driver can feel. The engine makes normal power, idles smoothly, and nothing sounds wrong — while a failing oxygen sensor quietly runs the mixture rich and slowly poisons the catalytic converter.

The distinction that matters is not "do I feel it" but "what system is it." A borderline EVAP leak is a nuisance. An upstream oxygen sensor drifting out of range is a cheap part that, ignored, becomes an expensive one.

You can't tell which you have without reading the code.

• Don't disconnect the battery to clear the light. It may erase some stored data, but it does not clear permanent codes, and it resets your readiness monitors — which means if you have an emissions test coming up, you've just guaranteed a failure until you complete enough drive cycles.
• Don't use a device that automatically erases codes. These exist and they're sold cheaply. They clear the symptom, leave the fault, reset your monitors, and make an eventual real diagnosis harder.
• Don't clear the code before someone diagnoses it. The freeze frame data is the most valuable diagnostic information available, and clearing the code deletes it. If you're taking the car to a mechanic, leave the code in place.

The readiness monitors turn this into a buyer's tool.

If you're inspecting a used car and the monitors read "not ready" or "incomplete" on a vehicle that's been driven regularly, the codes were cleared recently. A seller who erased a check engine light the morning of your visit leaves exactly that trace — and the light will return after a few dozen miles, by which point the car is yours.

This is one of the reasons a scanner belongs in the bag when you go look at a car. Our used car inspection checklist covers the rest of what to check, and the GM warranty guide explains how open codes interact with remaining factory coverage.

Be precise about what the tool does, though: a consumer scanner reads fault codes and readiness status. It does not reliably read stored odometer values, so it tells you nothing about mileage tampering. For that, the title record is the source — see our guide to what a salvage or rebuilt title means.