SETTLED_CLEANUP_UNOWNED
onSettled returned a cleanup in an unowned (out-of-band) scope.
What you saw
- Kind:
lifecycle - Severity:
error(broken behavior)
The console report opens with [SETTLED_CLEANUP_UNOWNED] 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: "SETTLED_CLEANUP_UNOWNED", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
onSettled returned a cleanup while running in an unowned scope, so the cleanup cannot be honored.
How to fix it
Call the setup helper from an owned scope (the component body), not from an event handler, tracked effect, or another onSettled.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while SETTLED_CLEANUP_UNOWNED 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.