Pending vs stored OBD2 codes: what is the difference?

Date: 2026-08-21T00:00:00+00:00 - (Skid Vis)

A pending OBD2 code records a potential malfunction that the onboard diagnostic system has detected but may still be evaluating. A stored code usually means the scanner retrieved a code retained by the vehicle after a malfunction met the applicable storage criteria. Scanner labels vary, so “stored” may correspond to confirmed, active, or malfunction-indicator-lamp-related code categories depending on the vehicle and tool.

Do not assume that every pending code becomes stored after exactly two trips, or that every stored code means the check-engine light must be on now. Monitor strategy, operating conditions, vehicle rules, and scanner terminology all matter.

Pending means the system detected a potential malfunction

A pending diagnostic trouble code, or DTC, is evidence that a monitor detected a malfunction but has not yet completed the applicable confirmation process. It is not simply a less important version of a stored code. It captures a stage in the vehicle’s evaluation process.

California’s light-duty OBD II regulation for passenger cars, light-duty trucks, and medium-duty vehicles defines a pending fault code as the DTC stored on initial malfunction detection, typically on one driving cycle, before MIL illumination under the regulation’s monitoring requirements.

That definition is much closer to the vehicles most drivers scan. It still does not create one timing schedule for every monitor because the same regulation contains monitor-specific rules and allows approved alternate statistical protocols.

The California light-duty regulation defines a confirmed fault code as the DTC stored when the OBD II system confirms that a malfunction exists, typically on the second driving cycle in which the malfunction is detected. “Typically” matters because monitor-specific and approved alternate procedures can differ.

A consumer scanner may instead show a category named “stored.” Read that label as the tool’s presentation of data returned by the vehicle, not as proof that every manufacturer uses one identical maturation rule.

When a scan shows both pending and stored results, preserve the category attached to each code. Two entries with the same code number but different states can describe different points in the monitor’s evaluation and storage process.

How a pending code can mature

The California light-duty regulation sets out a general sequence:

  1. The OBD II system detects a malfunction and stores a pending fault code.
  2. If it detects the malfunction again before the end of the next driving cycle in which that monitor runs, the MIL illuminates and a confirmed fault code is stored.
  3. If the malfunction is not detected before the end of that next monitored driving cycle, the corresponding pending code is erased.

The regulation also contains exceptions and monitor-specific procedures. Certain conditions can require immediate MIL illumination and confirmed-code storage, while manufacturers can seek approval for alternate statistical protocols that remain effective and timely.

That is why “pending always becomes confirmed on the second trip” is too broad. The relevant monitor must run, the fault must meet its criteria, and an applicable exception or approved strategy may use another path.

The check-engine light does not tell the whole story

A pending code can exist before the malfunction indicator lamp, or MIL, is commanded on. Under the California light-duty regulation’s general protocol, MIL illumination accompanies confirmed-code storage after the malfunction is detected again during the next monitored driving cycle.

The reverse needs nuance too. A stored or previously confirmed code can remain available after the MIL turns off. The regulation uses separate criteria for extinguishing the MIL and erasing a confirmed fault code, so current lamp status and retained-code status are not identical.

So scan results and dashboard-light status answer different questions:

  • Pending code: Has the system detected a potential malfunction that may still be under evaluation?
  • Stored or confirmed code: Has the system retained a code after meeting the relevant storage criteria?
  • MIL status: Is the vehicle currently commanding the warning lamp under its applicable rules?

Always consider all three. Also follow any vehicle warning that requires immediate action, regardless of code category.

Freeze-frame data can change as a code matures

Freeze-frame data is a snapshot of operating conditions associated with a detected event. It may include useful context, but availability and presentation vary by vehicle and scan tool.

The California regulation requires freeze-frame conditions to be stored when a malfunction is detected. Its general SAE J1979 provisions tie freeze-frame storage and erasure to either pending or confirmed fault codes. California’s 2021 final OBD II regulation order adds detailed SAE J1979-2 handling in which a pending code can mature to a confirmed code while freeze-frame data is retained or updated according to the specified frame.

That means you should not assume every code has a separate immutable snapshot or that every protocol presents the same number of frames. Before clearing anything, record whatever freeze-frame information the vehicle and scanner provide, along with the code state and current MIL status.

What clearing codes does

A scan-tool clear request changes diagnostic evidence. It is not a repair.

The California light-duty regulation uses separate erasure criteria for confirmed and permanent fault codes. The California Bureau of Automotive Repair explains that permanent DTCs cannot be erased with a scan tool or battery disconnect; the OBD II system clears them after it verifies that the previously identified defect is no longer present.

Clearing can also remove freeze-frame information associated with an erasable code. Once that context is gone, reproducing the original conditions may be difficult. Record first.

Readiness status is another concern near an emissions inspection. The California Bureau of Automotive Repair reference lists how many incomplete monitors can pass the OBD portion of its Smog Check inspection. Check the vehicle service information and local inspection rules before clearing codes near an inspection date.

Most importantly, clearing a code does not correct the condition that caused it. If the fault remains and the relevant monitor runs again, diagnostic information can return under the vehicle’s applicable logic.

Practical next steps after scanning

Use a repeatable process while parked:

  1. Record each exact DTC, including its pending, stored, confirmed, or permanent label.
  2. Note whether the MIL is on, off, or flashing.
  3. Save available freeze-frame information before clearing anything.
  4. Record relevant symptoms, warning messages, and recent work on the vehicle.
  5. Check manufacturer service information for the code, monitor conditions, and diagnostic procedure.
  6. Have a qualified automotive professional diagnose safety concerns or faults outside your experience.
  7. Re-scan after the prescribed inspection, test, or repair rather than guessing when a monitor should run.

EPA’s federal OBD rule history says diagnostic information is stored to assist technicians in diagnosis and repair. “Assist” is the right boundary. A code identifies detected conditions or a monitored system. It does not by itself prove which part should be replaced.

Avoid using code descriptions as parts lists. Wiring, connectors, operating conditions, related systems, and component tests can all matter to a qualified diagnosis.

Checking both states with OBD Auto

OBD Auto’s fault-code scanner scans stored and pending codes on Android and shows bundled offline descriptions where available. It requires a compatible Bluetooth Classic OBD-II adapter that is already paired in Android settings. BLE-only and Wi-Fi-only adapters are unsupported.

Its Android Auto support is phone-projected: templates show selected telemetry and link to fault information. It does not support Android Automotive OS or install on a vehicle’s built-in system. Perform scanning, adapter setup, code clearing, and other phone controls while stationary.

Whether you use OBD Auto or another scanner, keep the distinction clear: pending is potential, stored or confirmed reflects additional retention criteria, and neither state is a complete diagnosis.