SSR_RENDER_ERROR_CONTAINED
Server render error routed by a boundary: data.handling fallback / client / failed (observe + dev).
What you saw
- Kind:
ssr - Severity:
error(broken behavior)
The console report opens with [SSR_RENDER_ERROR_CONTAINED] and the message, then an in line naming the owners that enclose the subject, root first, and an at line with the source location when the code was compiled with one.
In a captured artifact the same finding is an event with code: "SSR_RENDER_ERROR_CONTAINED", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
A component threw during a server render and a boundary routed the error; data.handling says how.
fallback — an <Errored> rendered its fallback (the response was a 200 showing the fallback; if this fires on every request the fallback is the page).
client — the enclosing <Loading> fragment rejected and the client re-rendered the subtree after hydration (the user paid a client render and a flash).
failed — nothing contained it and the request failed.
The server runtime reports on the same channel, with the same in <App> › <Page> line.
Two groups.
Findings (SSR_RENDER_ERROR_CONTAINED, SSR_SUBTREE_ABANDONED, SSR_STREAM_ABANDONED, LATE_HEADER_WRITE, DYNAMIC_ASYNC_COMPONENT, SERVER_ERROR_SANITIZED, FRAME_MARKER_CORRUPTED) are facts about a render that exist in observe builds too — an APM sees them in production; in dev they print.
Checks (the rest, SSR_BOUNDARY_WATERFALL and SSR_CLIENT_CONTENT_MASKED included) are dev-only guidance.
A captured artifact from a server render carries both.
How to fix it
In every case the repair is the error in data.error, in the component ownerPath names; then consider whether an <Errored> closer to the throw would contain it more narrowly.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while SSR_RENDER_ERROR_CONTAINED is among them, with the events as evidence; after the fix, the code is gone from artifact.diagnostics.
Check for regressions in tests shows the loop and the Vitest matcher form.
Learn more
- Diagnostics: every code, with its kind, severity, and trigger.
- Debugging reactivity: how to read a report and what each group of codes points at.