How to Tell Whether a Fault Code Is Current, Pending or Permanent

Start with the result: what each status means for your next move

Knowing whether a fault code is current, pending or permanent changes what you do next. A current (active) code usually means the problem is present now and may require immediate repair. A pending code indicates an intermittent or one-off fault that hasn’t met the manufacturer’s threshold to become active. A permanent code is recorded after the vehicle’s computer has confirmed a recurring fault and won’t clear by simply disconnecting the battery or using a basic clear command.

How to read scanner output for code status quickly

Most modern OBD2 scanners show code types or status directly. Use the focus keyphrase "current pending permanent codes" when you scan so you can match terminology to the display.

• If the scanner lists codes under headings like “Active,” “Stored,” “Pending,” or “Permanent,” read those labels first—Active/Current means the ECU still sees the fault.
• Some entry-level readers only show DTCs without status. In that case, you’ll need the scanner’s Mode 1/3/7/2 functions or a higher-end reader that reports “Pending/Confirmed/Permanent.”
• Look for Mode 7 results (often labeled “Pending Codes” or “Pending DTCs”)—these are faults that occurred but didn’t meet criteria to illuminate the MIL (check engine light).

Step-by-step: confirm a code is current (active)

1. With the engine running or in key-on engine-off where required, read live codes. If the code appears in the active/confirmed list and the MIL is on, it’s current.
2. Check freeze-frame data (if available) to see recent sensor values and conditions when the ECU logged the fault—this helps confirm it’s a recent event, not a past transient.
3. Run live data for relevant parameters (oxygen sensors, fuel trim, MAF, misfire counts) to see if the fault is reproducible in real time.

Step-by-step: identify pending (intermittent) codes

Pending codes are caught when the ECU sees a fault during a single drive cycle but hasn’t confirmed it across required cycles.

1. Read Mode 7/Pending DTCs on your scanner. If a code appears only there and the MIL is off, it’s pending.
2. Check freeze-frame: if conditions were unusual (cold start, high load), the fault may be context-specific.
3. To decide whether to act, reproduce the condition that triggered the code—short test drives under similar loads often confirm or clear a pending code.

Step-by-step: recognize permanent DTCs and why they matter

Permanent codes indicate the ECU has verified a fault and expects it to be repaired; these survive a code clear until the repair is completed and the readiness checks pass.

• Your scanner may show “Permanent,” “Permanently Stored,” or list the code but block clear commands for it.
• Permanent DTCs keep the vehicle in a state where onboard readiness monitors related to that system won’t show as complete until the fault is fixed and the car completes a full drive cycle.
• Manufacturers use permanent DTCs to prevent tampering—clearing them without repair can leave the car noncompliant with emissions checks.

Use readiness monitors and drive cycles to verify status

Readiness monitors tell you whether system self-tests have completed since the last clear—and they’re directly tied to pending vs permanent behavior.

• If a pending code exists but relevant monitors are “not ready,” it may clear after normal driving. If permanent codes exist, monitors related to that subsystem will stay not ready until repair and successful tests.
• Perform a manufacturer-recommended drive cycle after repair to allow monitors to run. If the code remains but becomes permanent, further diagnosis is needed.

Practical checks and tests to avoid misdiagnosis

• Always verify the vehicle’s VIN and scanner compatibility—some manufacturers report status differently.
• Use freeze-frame and live data rather than clearing codes and retesting immediately; clearing can remove diagnostic clues.
• Watch for multiple related codes—an electrical fault or vacuum leak can produce several pending codes before one becomes permanent.
• Consider battery state and recent repairs: a recently cleared code plus a low battery or loose connector can cause monitors to reset and produce misleading pending codes.

When to repair now, when to monitor, and when to schedule a full diagnosis

If a code is current and the MIL is flashing or the vehicle is drivability-impaired (stalls, misfires, loss of power), repair immediately. For a non-flashing current code with no symptoms, prioritize by safety and emissions risk—oxygen sensor or EVAP leaks often need timely attention. For pending codes, monitor and reproduce before paying for parts; many clear after a couple of successful drive cycles. For permanent codes, treat them as confirmed: either perform or schedule the diagnosis and repair, because simple clearing won’t remove them.