Pending trouble codes are early fault records that your car’s engine computer saves when a self-test fails once but the problem has not yet been confirmed. They often appear on a scan tool while the check engine light stays off, which surprises many owners the first time they plug in a reader.
This article explains what a pending code represents, why on-board diagnostics use a waiting stage at all, how a pending code either matures or fades away, and how to treat one sensibly. The goal is to help you read these early warnings calmly and use them to plan testing rather than guesswork.
Why Your Car Keeps a Fault on Probation
On-board diagnostics, generation two (OBD-II), is the self-monitoring system required on US cars and light trucks from model year 1996. The powertrain control module, the computer that manages the engine and often the transmission, runs tests called monitors on sensors, emissions parts and engine behavior.
A single failed test does not always mean a real fault. A loose fuel cap, a cold morning, a puddle splash or a brief sensor glitch can trip a monitor once. If the computer lit the warning lamp for every one-time event, drivers would face constant false alarms and unnecessary shop visits.
The pending stage solves this problem. The computer records the failure as pending, keeps watching, and waits to see whether the same fault appears again under similar conditions. In effect, the fault sits on probation until the system has enough evidence to confirm it or let it go.
What a Pending Code Actually Tells You
A pending code tells you that a specific monitor detected a condition outside its expected range during the current or last completed drive cycle. A drive cycle is a sequence of driving, from a cold start through warm-up and varied operation, that gives the monitors a chance to run.
The code uses the same five-character format as any other trouble code. For example, P0171 means system too lean on bank 1, and P0442 means a small evaporative emissions leak was detected. The letter, digits and definition are identical whether the code is pending or confirmed.
What differs is the status. Pending means the fault has been seen but not yet verified on a following trip. It is a clue about where to look, not proof that a part has failed, and certainly not an instruction to replace whatever the code description mentions.
How a Pending Code Moves Through Its Life
Every pending code follows one of a few paths. Understanding them helps you predict what the check engine light will do next and when to schedule testing. The exact trip counts and conditions are set by regulation and by each manufacturer, so treat this as a general pattern.
- The monitor fails once, and the computer stores a pending code without turning on the lamp.
- On a later trip, the same monitor runs again under similar conditions and either passes or fails.
- If it fails again, the code usually matures into a confirmed code and the check engine light turns on.
- If it keeps passing, the pending code is eventually dropped from the pending list.
- Some severe faults skip the waiting stage and light the lamp immediately.
Because of these rules, a pending code can disappear on its own, and that is not a sign that the scan tool was wrong. It only means the fault did not repeat. A recurring pattern of the same pending code is still worth investigating.
Pending Codes Compared With Other Code Types
Scan tools show trouble codes in several groups. Knowing how pending codes relate to the others prevents confusion when the same code appears on more than one screen.
Pending Versus Confirmed Codes
A confirmed code, also called a stored or matured code, means the fault was verified, usually across more than one trip. For emissions-related faults, a confirmed code typically turns on the check engine light, which is officially called the malfunction indicator lamp (MIL).
A pending code has not reached that point. The same definition can exist in both lists at once, which simply means the fault was confirmed and also seen during the most recent drive cycle.
Pending Versus Permanent Codes
Permanent codes are a protected copy of confirmed emissions codes that a scan tool cannot erase. They clear only after the vehicle itself verifies that the fault is gone.
A pending code never becomes permanent directly. It must first mature into a confirmed code that turns on the lamp. Until then, it remains the most temporary type and is erased whenever codes are cleared.
Pending Codes and Freeze Frame Data
Freeze frame data is a snapshot of conditions, such as engine speed, coolant temperature and load, recorded when a fault is logged. It is most often linked to confirmed codes.
Some vehicles also capture data at the pending stage, while others do not. If your tool shows a freeze frame alongside a pending code, use it to understand when the fault occurred.
Where to Find Pending Codes on a Scan Tool
Generic OBD-II scan tools read pending codes through a standard request known as Service $07, often called Mode 7. Basic readers may simply show a tab or line labeled pending, while others combine all codes in one list and mark each with its status.
To read them, locate the 16-pin diagnostic connector, which is usually under the dashboard on the driver’s side. With the parking brake set and the ignition on, or the engine running outdoors, connect the tool and follow its menu to the code or pending code screen.
If your tool shows no pending section at all, check its manual. Some very simple readers display only confirmed codes. In that case, an early fault may stay hidden until it matures, which is one reason many DIYers prefer a tool that clearly separates code status.
Common Situations That Create Pending Codes
Certain conditions produce pending codes more often than others. Evaporative emissions monitors, which check the fuel vapor system for leaks, are a classic example. A fuel cap that was not tightened after refueling can trigger a pending small-leak code that later clears once the cap seals properly.
Misfire monitors can log a pending code after a single rough start, especially in damp weather or with marginal ignition parts. Oxygen sensor and fuel trim monitors may record pending lean or rich codes after unusual driving, such as long idling, heavy towing or running very low on fuel.
None of these examples means the fault is imaginary. A cap that seals poorly, an aging coil or a small vacuum leak can all start as an occasional pending code. The pending stage simply gives you an early look before the problem becomes steady enough to confirm.
What Not to Do With a Pending Code
Pending codes are easy to misread because they arrive without a warning lamp. A few habits turn a helpful early warning into wasted money or a missed fault.
- Do not buy and install a part based only on the code description; test the circuit and component first.
- Do not clear codes just to make the pending entry disappear, because that also erases useful data and resets readiness monitors.
- Do not ignore a pending code that returns after every few trips, since repetition is evidence of a real condition.
- Do not read the scan tool while driving; let a passenger watch the screen or review data after parking.
Clearing a pending code does not fix anything. It only removes the record and forces the monitors to start over, which can delay an inspection. A patient, test-first approach keeps the useful information intact.
How Pending Codes Help With Repair Verification
Pending codes are valuable after a repair. Once a fix is made, the monitor that originally failed must run again. If it fails on that first trip, a pending code appears quickly, often before the check engine light would return.
This makes the pending list a fast way to check your work. After a repair and a drive that covers the conditions the monitor needs, a clean pending list suggests the fault did not reappear. A returning pending code means the root cause may still be present.
Remember that a monitor must actually run for this check to mean anything. If the drive was too short or the conditions were not met, the absence of a pending code proves little. Readiness status on your scan tool shows which monitors have completed since codes were last cleared.
Pending Codes and Emissions Inspections
A pending code by itself does not turn on the check engine light, so it is less visible during a routine inspection. However, the fault behind it may mature before test day, and many state emissions programs also check readiness monitor status, which resets to not ready if codes are cleared.
Rules differ by state. Some programs use a plug-in OBD test, some allow a limited number of incomplete monitors, and some exempt certain model years. Your state emissions program website or office is the correct source for current requirements in your area.
If you see a pending code shortly before an inspection, the safest approach is to diagnose and repair the cause, then drive normally so the monitors can complete. Trying to time the inspection around a pending code rarely works and can lead to a failed test later.
Building a Habit of Early Code Checks
Pending trouble codes reward owners who check them regularly. A quick scan every few weeks, or after a rough start or unusual smell, can reveal a developing problem while it is still intermittent and easier to trace.
Keep a simple log with the date, mileage, code and status each time you scan. Over time, that record shows whether a pending code is a one-time event or part of a pattern. It also gives a technician valuable history if you eventually need professional help.
When a pending code repeats or points to a system you are not equipped to test, consult the service manual or a qualified technician. Treat the code as the start of a diagnosis, verify the cause with testing, and let the pending stage give you time to fix problems before they grow.