Your Telegram bot is silent.
OpenClaw says it's running.

Silent message drop

Telegram stops delivering messages to the bot. No error in OpenClaw logs. No webhook failure. The bot is alive. Messages are gone. Users think you broke something.

Orchesis detects it in 90 seconds — Compares expected message rate against actual. Telegram alert with channel, time, and last successful delivery.

VPN kills your bot at 3am

VPN rotation disconnects Telegram long-polling. OpenClaw doesn't know. Retries silently fail. Your bot is offline until someone manually restarts it. Nobody's watching at 3am.

Orchesis detects VPN failure in 2 minutes — Monitors polling continuity. Sends Telegram alert with reconnect command before the first user notices.

Watchdog cascade

18 agents sharing one OAuth profile. Agent A refreshes the token. Agent B uses the stale one, gets 401, falls back to Opus at $0.186/turn. Watchdog triggers. All 18 agents restart simultaneously. $636/month from one config decision.

Orchesis identifies the cascade root cause — Cross-agent token tracking shows which agent caused the refresh race. One fix, not 18 restarts.

Config schema cost on every message

Default OpenClaw config injects the full configuration schema into every system prompt. Every Telegram message triggers a call with ~100,000 extra tokens. Breaks Anthropic prompt caching. You pay full price on every call instead of 90% savings.

orchesis verify finds it in 30 seconds — Shows exact overhead, cost per message, and the one-line fix.

Why is my OpenClaw Telegram bot not receiving messages?

The most common causes are silent webhook failures, VPN disconnection during Telegram long-polling, and Telegram rate limiting after a loop storm. Orchesis monitors all three continuously and sends a Telegram alert with the specific cause within 90 seconds of the drop.

Does OpenClaw Telegram work with VPN in Russia?

Yes, but VPN instability is the leading cause of silent bot failures. When VPN rotates or reconnects, Telegram long-polling drops without an error visible in OpenClaw logs. Orchesis detects the polling gap and alerts you with a reconnect command before users notice.

How does Orchesis detect Telegram silent drops?

Orchesis maintains a baseline of expected message delivery rate per channel. When actual delivery falls below baseline for 90 seconds, it sends a Telegram alert with the channel, timestamp, and last successful delivery time. No false positives from normal quiet periods.

What is the OpenClaw watchdog cascade problem?

When multiple OpenClaw agents share one OAuth profile, a token refresh by one agent invalidates all others. Each agent gets a 401 error, triggers the watchdog, and restarts. All agents restart simultaneously, flooding the LLM API and creating a cost spike. Issue #43178 documents a case with 18 agents and $636/month in waste.

Does Orchesis work with WhatsApp and Discord too?

Yes. Orchesis monitors all traffic between your OpenClaw agent and the LLM API regardless of channel. Telegram, WhatsApp, Discord, and WebChat are all covered by the same proxy. Channel-specific detection patterns apply per channel type.

What happens if Orchesis goes down?

Your agents fall back to direct API calls automatically. Orchesis is not in the critical path. If the proxy is unavailable, OpenClaw routes directly to the LLM provider. Zero downtime risk to your bot.

Is Orchesis free?

Yes. MIT license. Self-hosted. No telemetry. No vendor lock-in. No usage limits.