REACTIVITY_HALTED
Uncaught error escaped every boundary; scheduling stopped (reported, cause to reportError).
What you saw
- Kind:
error - Severity:
error(broken behavior)
The console report opens with [REACTIVITY_HALTED] 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: "REACTIVITY_HALTED", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
An earlier uncaught error halted the reactive system; subsequent updates are ignored.
How to fix it
Do not treat this code as the bug — find the original error above it (or add an error boundary with <Errored>) and fix that.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while REACTIVITY_HALTED 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.