Health Checks (CLI)
Short guide to verify channel connectivity without guessing.Quick checks
wednesdayai status— local summary: gateway reachability/mode, update hint, linked channel auth age, sessions + recent activity.wednesdayai status --all— full local diagnosis (read-only, color, safe to paste for debugging).wednesdayai status --deep— also probes the running Gateway (per-channel probes when supported).wednesdayai health --json— asks the running Gateway for a full health snapshot (WS-only; no direct Baileys socket).- Send
/statusas a standalone message in WhatsApp/WebChat to get a status reply without invoking the agent. - Logs: tail
/tmp/openclaw/openclaw-*.logand filter forweb-heartbeat,web-reconnect,web-auto-reply,web-inbound.
Deep diagnostics
- Creds on disk:
ls -l ~/.openclaw/credentials/whatsapp/<accountId>/creds.json(mtime should be recent). - Session storage:
wednesdayai session-storage status(backend, readiness, legacy JSONL import progress) andwednesdayai sessions --jsonfor the index rows; both go through the running gateway when one runs. - Relink flow:
wednesdayai channels logout && wednesdayai channels login --verbosewhen status codes 409–515 orloggedOutappear in logs. (Note: the QR login flow auto-restarts once for status 515 after pairing.)
When something fails
logged outor status 409–515 → relink withwednesdayai channels logoutthenwednesdayai channels login.- Gateway unreachable → start it:
wednesdayai gateway --port 18789(use--forceif the port is busy). - No inbound messages → confirm linked phone is online and the sender is allowed (
channels.whatsapp.allowFrom); for group chats, ensure allowlist + mention rules match (channels.whatsapp.groups,agents.list[].groupChat.mentionPatterns).
Dedicated “health” command
wednesdayai health --json asks the running Gateway for its health snapshot (no direct channel sockets from the CLI). It reports linked creds/auth age when available, per-channel probe summaries, session-store summary, and a probe duration. It exits non-zero if the Gateway is unreachable or the probe fails/timeouts. Use --timeout <ms> to override the 10s default.