ClawCloudClawCloud.sh
How it worksModelsPricingCompareGuidesBlog
Log in
DeployDeploy Now
ClawCloud logoClawCloud

Managed OpenClaw AI assistant hosting on dedicated cloud servers.

Deploy now →
Product
ModelsPricingCompare PlansOpenClaw HostingOpenClaw VPSOpenClaw CloudTelegram BotDiscord BotFeishu BotUse CasesFAQ
Resources
GuidesBlogTopicsOpenClawGitHub
Company
ContactTerms of ServicePrivacy Policy
© 2026 ClawCloud. All rights reserved.
All guides

Understanding OpenClaw Instance Health Checks

Published July 7, 2026

The ClawCloud dashboard surfaces health checks reported directly by your instance's agent. When your bot detects a problem, a notice appears at the top of the instance panel — no SSH required to find out what's wrong.

ClawCloud dashboard instance panel showing a yellow warning notice for channel conflict

How the checks work

The Checks panel polls your instance every 10 seconds. Each poll asks the agent on your server to scan the last 40 lines of the OpenClaw gateway log for known error patterns. Checks that find a problem are returned as notices with a severity level (warning or info). They appear and clear automatically — no page reload needed.

Channel conflict

What you'll see: A yellow warning — "Bot token conflict detected."

This means another process is calling getUpdates on the same bot token at the same time as your OpenClaw instance. Only one polling process can hold a Telegram bot token at a time, so your bot stops receiving messages.

Common causes:

  • A local instance running on your laptop during testing
  • A previous deployment that wasn't fully stopped
  • Another person using the same bot token

Fix: Stop the competing process. You can also clear the conflict by opening this URL in your browser (replace <TOKEN> with your bot token):

https://api.telegram.org/bot<TOKEN>/deleteWebhook?drop_pending_updates=true

After that, go to the ClawCloud dashboard and use the Restart Gateway action to reconnect.

DM access restricted

What you'll see: A blue info notice — "DM access restricted."

Your bot's DM policy is set to pairing mode. Anyone messaging the bot directly gets "You are not authorized." until they're paired.

Fix: Open the Settings tab on your instance and enable DM access, or use the Unlock DM Access action from the instance actions menu. See how to unlock OpenClaw DM access for the full steps. To change the DM policy proactively, see How to Change the OpenClaw DM Policy.

Free model active

What you'll see: A blue info notice — "Free model active."

Your instance is currently running on a free model. This can happen if the plan's included credits were fully used before the next billing cycle reset, or if you manually switched to a free model.

Free models are rate-limited and may respond more slowly. To switch back, go to the Settings tab and pick a paid model. If your credits are exhausted, the switch takes effect immediately once they reset. See OpenClaw model tiers and free models for more.

Notices clear automatically

Notices don't require any manual dismissal. The Checks panel re-polls every 10 seconds, so once the underlying condition is gone — the conflict stops, DM access is re-opened, the model switches — the notice disappears on its own within a few seconds.

Ready to deploy?

Skip the setup — your OpenClaw assistant runs on a dedicated server in under a minute.

Deploy Your OpenClaw

Keep reading

Server ManagementClawCloud Platform UpdatesAll topics →
Post

What's New in OpenClaw 2026.4.14: GPT-5.4 Recovery and Telegram Topic Fixes

OpenClaw 2026.4.14 tightens GPT-5.4 turn recovery, improves Telegram forum-topic handling, and fixes Codex and custom-provider edge cases.

Post

Fix: OpenClaw managed reply reliability on ClawCloud

ClawCloud improved OpenClaw managed reply reliability so managed sessions recover from stale model state instead of failing before a usable reply.

Post

Fix: OpenClaw version reporting after manual upgrades

ClawCloud now shows the correct OpenClaw version after manual upgrades by checking the running process first, not the old install path.

Post

What's New in OpenClaw 2026.3.28: xAI Responses, Config Schema & Upgrade Notes

OpenClaw 2026.3.28 adds xAI Responses API, a config schema command, plugin approval gates, and stricter validation for old config keys.

Post

What's New in OpenClaw 2026.3.24: Image Generation, Heartbeat Savings & Upgrade Notes

OpenClaw 2026.3.24 adds image generation model routing, isolated heartbeat sessions that slash token use, loop detection, and removes the legacy bridge config.

Post

ClawCloud Now Supports OpenClaw Windows Cloud Servers

ClawCloud now provisions Windows cloud servers for OpenClaw. Get full RDP desktop access, Chrome pre-installed, and the same managed deploy flow.