tinyhumansai/openhuman · error
no channel components tracked yet
Error message
no channel components tracked yet
What it means
Doctor channel-health check: the component-status store contains zero channel components, so the fresh/stale loop over per-channel heartbeats had nothing to evaluate. Distinguishing this from a stale channel: no channel runtime ever registered, which on a fresh install with no channels connected is normal, but on a configured instance means the channels service is not spawning its workers.
Source
Thrown at src/openhuman/platform/doctor/core.rs:695
Utc::now().signed_duration_since(dt).num_seconds()
});
if status_ok && age <= CHANNEL_STALE_SECONDS {
items.push(DiagnosticItem::ok(
cat,
format!("{name} fresh ({age}s ago)"),
));
} else {
stale += 1;
items.push(DiagnosticItem::error(
cat,
format!("{name} stale (ok={status_ok}, age={age}s)"),
));
}
}
if channel_count == 0 {
items.push(DiagnosticItem::warn(
cat,
"no channel components tracked yet",
));
} else if stale > 0 {
items.push(DiagnosticItem::warn(
cat,
format!("{channel_count} channels, {stale} stale"),
));
}
}
}
// ── Environment checks ───────────────────────────────────────────
fn check_environment(items: &mut Vec<DiagnosticItem>) {
let cat = "environment";
// gitView on GitHub (pinned to 7491200858)
Solutions
- If no channels are configured, connect one in the UI and re-run doctor
- Verify the channels service is enabled in the running ServiceSet
- Inspect core logs for channel runtime startup failures if channels are configured but untracked
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at src/openhuman/platform/doctor/core.rs:695 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/ef42f4389e08bb0f.
Report an issue: GitHub.