The point at which a code returns can help define the operating condition that triggers it. Clearing successfully with the engine stopped does not demonstrate a repair, because the relevant monitor or load may not yet have operated.
Record the first return
State whether the code returns during cranking, immediately after startup or after a delay. Include the status and any snapshot information. If a repair was performed, retain both the original and subsequent reports.
The workshop should identify which test conditions apply to that code and reproduce them safely where appropriate. Do not keep clearing records after each start, as that can remove useful context. A component may behave differently under load or temperature, but the timing alone cannot distinguish wiring, supply, sensing or internal controller causes. Ask for the repair recommendation to be supported by measurements made during the condition that actually causes the fault to return.
Related help
- Diagnostic Trouble Code Suffixes: Why the Extra Characters Matter
- A Fault Is Present but No Code Is Stored
Browse all fault guides or use the vehicle module finder to prepare your enquiry. Include the vehicle, symptoms, complete fault codes and any previous test results. Assessment scope and compatibility must be confirmed before booking or sending a unit.