# Self-Healing CI: Recovering a ChromeDriver Download Version Mismatch

> A ChromeDriver that fails to download a matching version is a transient setup race, not a test bug. See the manual fix and how self-healing CI re-resolves and retries.

Source: https://latchkey.dev/learn/self-healing-ci/self-healing-chromedriver-version-mismatch  
Updated: 2026-06-26

A ChromeDriver setup that fails to fetch a matching version usually hit a transient download or resolution blip, not a permanently incompatible driver -- re-resolving and retrying clears it.

## What makes a failure safely retryable

Automatic retry is only correct for failures that are genuinely transient. Retrying a deterministic failure wastes minutes and hides a real defect, so the classification matters more than the retry mechanism.

- Safe to retry: network timeouts, registry 5xx, transient DNS failures, a service container that was not ready, a spot instance reclaimed mid-run.
- Not safe to retry: assertion failures, compile errors, lint violations, anything that fails identically on every attempt.
- Ambiguous, and worth investigating rather than retrying: out-of-memory kills, disk exhaustion, and flaky tests. These repeat under load and a retry only hides the trend.
- Always record that a retry happened. A pipeline that silently retries is a pipeline whose real failure rate you do not know.

## FAQ

### What causes Self-Healing CI: recovering a ChromeDriver download version mismatch?

A browser-test setup step fails because ChromeDriver could not download a build matching the installed Chrome, or the download itself failed. Compatible versions exist; the resolution/download hit a transient blip. A human re-runs the setup -- re-resolving the matching driver -- and it installs cleanly.

### How do I fix Self-Healing CI: recovering a ChromeDriver download version mismatch manually?

[object Object]

### Can Self-Healing CI: recovering a ChromeDriver download version mismatch be fixed automatically?

A failed driver resolution/download has a recognizable transient signature when a compatible driver does exist, and the safe response is to re-resolve and retry. A self-healing CI pipeline detects the setup failure, retries driver resolution and download, and only escalates if no compatible driver is genuinely available, distinguishing a

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt