Home

Switch language

Start Install GuideQuick StartDocs Overview
Docs ChannelsModels & APIGateway OpsTools & Skills
More ArticlesResourcesHelp Center
Get Started
Documentation navigation Gateway Ops
Gateway Ops 2 sections

Health Checks

Health Checks

The goal of health checks is to break vague "it feels broken" reports into verifiable layers. Local summary, deep probes, Gateway health snapshots and channel session state all answer different questions and use different commands.

Four Levels of Checks

Local summary

openclaw status
openclaw status --all

Deep probe

openclaw status --deep

Gateway health snapshot

openclaw health --json

Check directly inside chat

/status

What to Check First When It Breaks

If WhatsApp or WebChat stops receiving messages, check the credential file timestamps and channel status before blaming the model.

If the Gateway is unreachable, get the process up first with openclaw gateway --port 18789 --force or service commands, then continue to health probes.

health --json does not directly talk to low-level sockets like Baileys. It summarizes the health view from the running Gateway.