tinyhumansai/openhuman · error
[subconscious] setInterval failed:
Error message
[subconscious] setInterval failed:
What it means
Failure of setIntervalMinutes in useSubconscious: the interval was applied optimistically to local state, then openhumanHeartbeatSettingsSet({interval_minutes}) rejected. The catch warns only — like setMode, local state keeps the optimistic value while the persisted interval is unchanged, until a later refresh corrects the display.
Source
Thrown at app/src/hooks/useSubconscious.ts:155
await openhumanHeartbeatSettingsSet({ subconscious_mode: newMode });
await refresh();
} catch (err) {
console.warn('[subconscious] setMode failed:', err);
setError(err instanceof Error ? err.message : 'Failed to update mode');
} finally {
setSettingMode(false);
}
},
[refresh]
);
const setIntervalMinutes = useCallback(async (minutes: number) => {
if (!isTauri()) return;
setIntervalState(minutes);
try {
await openhumanHeartbeatSettingsSet({ interval_minutes: minutes });
} catch (err) {
console.warn('[subconscious] setInterval failed:', err);
}
}, []);
useEffect(() => {
if (!enabled) return;
refresh();
const interval = setInterval(refresh, 5000);
return () => {
clearInterval(interval);
fetchingRef.current = false;
};
}, [refresh, enabled]);
const isTriggering = useCallback(
(kind: TriggerKind) => triggeringKinds.has(kind),
[triggeringKinds]
);
View on GitHub (pinned to 7491200858)
Solutions
- Re-read settings via refresh() to reconcile local vs persisted interval
- Validate the minutes value against the backend's allowed range before sending
- Check core RPC health for persistent failures
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at app/src/hooks/useSubconscious.ts:155 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17).
Data as JSON: /api/errors/a37d1bbe559f0506.
Report an issue: GitHub.