If your AI agent has stopped responding to messages, follow these diagnostic steps in order. Most issues are resolved within the first three steps.
Step-by-step diagnosis
Check server status on your Dashboard
Open your OneClickClaw dashboard and look at the server status indicator. A green dot means your server is online and healthy. If you see red or offline, your server needs attention. See the Server Offline article for next steps.
Check the Event Viewer for recent errors
On your Overview page, scroll down to the Event Viewer terminal. Look for recent error events (shown in red). These often reveal the exact cause, such as a failed API call, a configuration issue, or a resource limit.
Verify your API key is valid
Go to your AI provider's dashboard (e.g., console.anthropic.com) and check that your key is still active and has available credits. An expired or rate-limited key is the single most common cause of a silent agent.
Try sending a test message on a different channel
If you have multiple channels connected (e.g., Telegram and Discord), send a test message on the other channel. If the agent responds there, the issue is with the specific channel connection, not the agent itself.
Reboot the server
Go to your Server Details page and click the Reboot button. This restarts the OpenClaw process and clears any stuck states. The reboot typically completes within 2 minutes.
Download diagnostic bundle and open a support ticket
If none of the above resolves the issue, download a diagnostic bundle from your dashboard. Then open a support ticket and attach the bundle. Our team uses this data to diagnose the root cause.
Step 1: Dashboard
Step 2: Event Viewer
Step 3: API Key
Step 4: Test Channel
Step 5: Reboot
Step 6: Support
Common causes
- Expired or revoked API key: Your AI provider key was regenerated or ran out of credits. Update the key in your Agent Panel.
- Provider rate limit: You hit the requests-per-minute limit on your AI provider. Wait a few minutes or upgrade your provider plan.
- Server memory full: The server ran out of RAM and the OpenClaw process was killed. Reboot the server and consider upgrading your tier.
Tip
The most common cause is an expired or rate-limited API key. Check your provider's dashboard first.
Still not working?
If you have gone through all the steps and your agent is still not responding, open a support ticket from your dashboard. Include the diagnostic bundle and a description of when the problem started. Our support team responds within the timeframe guaranteed by your plan.
Note
Support response times: Starter (48 hours), Hobbyist (24 hours), Pro (4 hours).
Related articles: API Key Security, Server Status Indicators
