GoogleChrome/lighthouse · error · LighthouseError
MISSING_REQUIRED_ARTIFACT
MISSING_REQUIRED_ARTIFACT
Error message
Required {artifactName} gatherer did not run. What it means
Error "Required {artifactName} gatherer did not run." thrown in GoogleChrome/lighthouse.
Source
Thrown at core/lib/lh-error.js:415
DNS_FAILURE: {
code: 'DNS_FAILURE',
message: UIStrings.dnsFailure,
lhrRuntimeError: true,
},
/** A timeout in the initial connection to the debugger protocol. */
CRI_TIMEOUT: {
code: 'CRI_TIMEOUT',
message: UIStrings.criTimeout,
lhrRuntimeError: true,
},
/**
* Error internal to Runner used when an artifact required for an audit is missing.
* Requires an additional `artifactName` field for translation.
*/
MISSING_REQUIRED_ARTIFACT: {
code: 'MISSING_REQUIRED_ARTIFACT',
message: UIStrings.missingRequiredArtifact,
},
/**
* Error internal to Runner used when an artifact required for an audit was an error.
* Requires additional `artifactName` and `errorMessage` fields for translation.
*/
ERRORED_REQUIRED_ARTIFACT: {
code: 'ERRORED_REQUIRED_ARTIFACT',
message: UIStrings.erroredRequiredArtifact,
},
/** The page has crashed and will no longer respond to 99% of CDP commmands. */
TARGET_CRASHED: {
code: 'TARGET_CRASHED',
message: UIStrings.targetCrashed,
lhrRuntimeError: true,
},View on GitHub (pinned to 9515cd4e58)
Solutions
- Ensure the named gatherer is included in the active config (check onlyAudits/onlyCategories filters).
- If using a custom config, add the artifact's gatherer to the passes/artifacts list.
- Re-run without skipping the gatherer via skipAudits or gather flags.
Example fix
Ensure the gatherer for the required artifact runs in the configured pass before the audit that needs it.
When it happens
Trigger: Raised when a gatherer required by an audit did not run for the current gather mode.
Common situations: See trigger scenarios.
AI-assisted analysis of GoogleChrome/lighthouse@9515cd4e58 (2026-08-13).
Data as JSON: /api/errors/2bdb085d4f514c52.
Report an issue: GitHub.