Pending, stored and permanent codes

Pending codes: the early warning stage

A pending code appears the first time the powertrain control module detects a fault, before it has been confirmed across the number of consecutive drive cycles the manufacturer requires to consider it real rather than a one time anomaly. A pending code does not turn on the check engine light. It exists purely as an internal flag, visible only if you check with a scan tool.

Pending codes are useful precisely because they give you a warning before the dashboard light appears. If a fault clears itself before it repeats enough times, the pending code disappears on its own with no lasting record and the light never comes on.

Stored codes: the fault has been confirmed

A stored code, sometimes called a confirmed or active code, means the fault has repeated across enough drive cycles under the required test conditions that the module considers it real. This is the point where the check engine light turns on in most cases, and the stored code stays in memory along with its freeze frame data until it is either cleared with a scan tool, cleared by a battery disconnect, or in some cases automatically cleared after a defined number of consecutive trips pass without the fault recurring.

Permanent codes: the category most people misunderstand

A permanent code is a distinct category introduced specifically to prevent drivers from clearing a code right before an emissions test to fool the readiness monitors. Once a fault has been confirmed and set a permanent code, that code cannot be erased by a scan tool's clear function, nor by disconnecting the battery. It only clears once the vehicle completes enough successful drive cycles for the related monitor to pass on its own, confirming the actual repair worked rather than just erasing the record of the problem.

This is the mechanism behind a common frustration: a driver fixes a problem, clears the code, and the check engine light stays off, but the vehicle still fails an emissions test because a permanent code from that same fault is still present and has not yet had the chance to clear itself through normal driving.

Why this distinction changes how you should react to a scan result

Seeing a pending code calls for watching and rechecking rather than immediate repair panic, since the fault has not yet been confirmed and may resolve on its own. Seeing a stored code calls for actual diagnosis, since the module has confirmed the fault is real and repeatable. Seeing a permanent code after a repair calls for patience rather than repeated clearing attempts, since no amount of clearing will remove it before the monitor itself passes.

Confusing these three categories is a common source of wasted diagnostic time, such as replacing a part based on a pending code that would have cleared itself, or repeatedly clearing a permanent code expecting it to finally stick.

How to actually check which status a code is in

Most scan tools that read generic OBD2 data present these as separate menu items or separate labeled sections on the same screen, commonly titled something like pending codes, stored codes or confirmed codes, and permanent codes. A very basic code reader may only expose stored codes, in which case a pending or permanent code will not be visible even though it exists in the module's memory. Confirming which category a fault falls into before deciding on a next step avoids most of the confusion this distinction causes.