Fault Codes & Diagnostics

Why Intermittent Fault Codes Are the Hardest Job in the Workshop to Solve

17 November 2026 3 min read

The light was on this morning, the customer swears to it, and by the time it’s on your ramp it’s gone out and the car drives perfectly. This is the job every technician dreads, not because intermittent faults are rare, but because they’re genuinely harder to catch than a fault that’s there every time you look.

Why freeze frame alone isn’t enough

Freeze frame gives you one snapshot, the conditions at the exact moment the fault first triggered. For an intermittent fault, that single snapshot might not repeat, and a fault that only shows under a specific combination of temperature, load and vibration won’t necessarily reproduce on your ramp with the engine idling in a cold workshop. Useful, but treat it as one data point, not the whole picture.

What actually helps with an intermittent fault

  • Fuel trims over time, both long-term and short-term. A long-term trim that’s drifted suggests a chronic, ongoing issue the ECU has been quietly compensating for, even if no code has set yet, often the early warning before an intermittent code appears.
  • Data logging on a test drive matching the conditions the customer described, cold start, motorway speed, a particular corner or bump, rather than a static idle test in the workshop.
  • Wiggle testing, physically moving connectors and harness sections while watching live data or listening for a code to trigger, targeted at areas the vehicle’s history or your visual inspection flags as likely, previous repairs, areas near heat or vibration.
  • Pending codes, which show a fault has been detected but hasn’t yet met the criteria to fully mature and light the lamp, often the earliest and most reliable clue.

Connector or component, how to tell

An intermittent fault that correlates with wiggling a specific connector, or with bumps and rough roads, is almost always a connection problem, corrosion, a loose pin, a partially seated connector, rather than the component itself failing intermittently. A fault that correlates with temperature, appearing only once the engine’s fully warm or only on a cold start, points more towards a component with a thermal fault, a sensor or module that fails as it heats or cools. A fault with no obvious pattern at all is the hardest case and usually needs a longer data log, sometimes left connected over several days of normal driving, rather than a single test drive.

What workshops get wrong

The biggest mistake is giving up too early and either sending the car back with “no fault found” or replacing the most likely-looking part on a guess. Both cost you a comeback. A “no fault found” with no attempt at a data log or wiggle test tells the customer nothing and damages trust when the light comes back a week later. A guessed part replacement that happens to coincide with the fault going quiet for a while, purely because intermittent faults come and go on their own, can convince everyone the job’s fixed when it isn’t.

Set expectations before you start

It’s worth setting expectations with the customer up front too: an intermittent fault sometimes needs the car back for a longer data-logging period, or a specific journey repeated with the logger connected, rather than a same-day fix. Being upfront about that avoids a frustrated customer assuming the workshop simply couldn’t find anything. Where a portable logger can be left connected and collected by the customer to use normally for a few days, that’s often more productive than any single test drive a workshop can arrange, since real-world conditions are hard to fully recreate on demand.

Where the fault log points at dropouts across several modules rather than a single sensor, it’s worth reading our piece on tracing communication faults in the Fault Codes & Diagnostics category, and a proper data-logging capable scan tool from the Tools & Equipment category saves far more time than it costs.

Keep reading

More ECU guides