OpenClaw Adminv1.3.0

When the OpenClaw gateway stops responding, run the diagnostic ladder starting with 'openclaw status' and 'openclaw gateway status' to identify the issue. Then use 'openclaw doctor' for guided repairs, and if needed, check logs and config for silent failures like allowlist blocks.

If a Discord channel receives no responses despite no errors in logs, it's likely a dual allowlist issue where the channel is missing from both the guild-level and account-level channel allowlists. Fix by adding the channel to both sections in openclaw.json.

When both OAuth and API key exist for a provider, round-robin can cause unexpected profile switches. Lock the authentication order using 'auth.order[provider]' in config and check 'usageStats' for stale error counts that poison profile selection.

Two gateway instances sharing the same Discord bot token cause WebSocket reconnect storms, leading to connection instability. Ensure each gateway (main, rescue, etc.) uses a unique bot token to prevent conflicts.

When modifying openclaw.json, always read the current config, create a timestamped backup, and edit individual keys using 'openclaw config set' to avoid catastrophic data loss. Validate changes with 'openclaw config validate' before restarting only if necessary.

Offer a monthly retainer for ongoing maintenance, monitoring, and troubleshooting of OpenClaw installations, including gateway health checks, config optimization, and rapid issue resolution.

Provide on-demand diagnostic and repair services for OpenClaw outages, silent failures, or config corruption, with a guaranteed response time (e.g., 1 hour).

Create training courses or certifications for developers and admins on configuring, deploying, and troubleshooting OpenClaw, covering the diagnostic ladder, safe config editing, and common pitfalls.