---
title: "Grok Telegram Bot Not Responding: A Recovery Checklist"
description: "Troubleshoot a Grok-backed Telegram bot that does not reply by checking pairing, runtime state, xAI authentication, and delivery in order."
canonical: "https://deploy-hermes.com/troubleshooting/grok-bot-not-responding"
last-updated: "2026-08-23"
---

# Grok Telegram Bot Not Responding: A Recovery Checklist

> Troubleshoot a Grok-backed Telegram bot that does not reply by checking pairing, runtime state, xAI authentication, and delivery in order.

Canonical: https://deploy-hermes.com/troubleshooting/grok-bot-not-responding
Updated: 2026-08-23 · Search intent: troubleshooting
Category: [Troubleshooting](/troubleshooting)

When a Grok Telegram bot stops responding, check the path in order instead of replacing every credential. Telegram delivery, chat pairing, Hermes runtime execution, and xAI inference are separate boundaries with different evidence.

## Start at the channel

Confirm that the Telegram chat is the paired chat and that the sender remains allowed. Check whether the message appears in the workspace's incoming activity. If Telegram never delivered the update, the provider key cannot be the first suspect.

Use Telegram's Bot API documentation as the channel reference, but keep the bot token private. Do not create a second bot until you know the first token or webhook is actually the failing boundary.

## Check the Hermes run

If the message reached Hermes, inspect whether a run was created, claimed, and settled. A pending or blocked run needs its runtime or approval path; an errored run needs its recorded error. A missing run points back to routing or pairing.

Send a small request with no external side effect after each change. This gives you a clear before-and-after signal and avoids creating new work while the delivery path is uncertain.

## Check xAI last, then verify the reply

Confirm that the xAI connection is active and revalidate it if the error names authentication. If xAI accepts the key but the run fails, inspect model policy and runtime evidence rather than repeatedly pasting the same secret.

A fixed provider request is only half a recovery. Send a new Telegram test, confirm the reply arrives in the original chat, and record the complete path so the next incident starts with facts.

- No incoming event: inspect Telegram pairing and delivery.
- Incoming event but no run: inspect workspace routing and runtime claim.
- Run error: inspect provider authentication and execution evidence.

## Frequently asked questions

### What should I check first when the bot is silent?

Check whether the Telegram message arrived and whether the chat is paired and allowed. Then inspect the Hermes run before rotating the xAI key.

### Can a valid xAI key still produce no Telegram reply?

Yes. Provider authentication can succeed while pairing, runtime execution, approval, or Telegram delivery is still blocked.

## Sources

- [Telegram Bot API](https://core.telegram.org/bots/api) (as of 2026-08-23)
- [xAI inference API reference](https://docs.x.ai/developers/rest-api-reference/inference) (as of 2026-08-23)

---

- [Full documentation index](/llms.txt)
- [Complete site text](/llms-full.txt)
- [Developer portal](/developers)
- [OpenAPI contract](/openapi.json)
- [MCP server card](/.well-known/mcp.json)