gatsbyjs/gatsby · error
98001
98001
Error message
Built Rendering Engines failed validation.\n\nPlease open an issue with a reproduction at https://gatsby.dev/new-issue for more help.
What it means
Sentinel panic (id 98001, empty context) raised when the prebuilt rendering engines fail validateEngines(): the attached error carries the real validation failure, the static text is only a generic wrapper asking for a bug report.
Source
Thrown at packages/gatsby/src/utils/validate-engines/index.ts:36
)
) {
reporter.info(
`Skipping Rendering Engines validation as they are build for different platform and/or architecture`
)
return
}
const validateEnginesActivity = reporter.activityTimer(
`Validating Rendering Engines`,
{
parentSpan: buildSpan,
}
)
validateEnginesActivity.start()
try {
await validateEngines(directory)
} catch (error) {
validateEnginesActivity.panic({ id: `98001`, context: {}, error })
} finally {
validateEnginesActivity.end()
}
}
async function validateEngines(directory: string): Promise<void> {
const worker = new WorkerPool<typeof import("./child")>(
require.resolve(`./child`),
{
numWorkers: 1,
env: {
// Do not "inherit" this env var for validation,
// as otherwise validation will fail on any imports
// that OpenTracing config might make
GATSBY_OPEN_TRACING_CONFIG_FILE: ``,
},
silent: true,
}View on GitHub (pinned to e85d62f177)
Solutions
- Run `gatsby clean` and reinstall node_modules to restore the engine bundles
- Inspect the attached error for the underlying validation failure
- Open an issue with a reproduction at https://gatsby.dev/new-issue if it persists
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at packages/gatsby/src/utils/validate-engines/index.ts:36 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of gatsbyjs/gatsby@e85d62f177 (2026-08-26).
Data as JSON: /api/errors/a656afcaea3e8933.
Report an issue: GitHub.