telegram Unsupported schema node. Use Raw mode.

[placid swallow]

telegram Unsupported schema node. Use Raw mode.

[prime kraken]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[versed wraith]

did u get any answer ?

[ocean venture]

Based on my search, this error "Unsupported schema node. Use Raw mode" isn't a standard Clawdbot or Telegram Bot API error that I can find in the documentation or codebase.

Here's what I'd suggest to troubleshoot:

Check the gateway logs for more context:

clawdbot logs --follow

Look for the full error stack trace to see where this is coming from.

Possible causes:

1. Media/content format issue - Telegram might be rejecting a specific message format (especially with complex media or structured content)
2. Schema validation error - Could be related to how Clawdbot is constructing the message payload
3. Third-party integration - If they're using any other tools with Telegram (like a relay or custom bot), that could be the source

Quick things to try:

• Restart the gateway: clawdbot gateway restart
• Check if it happens with plain text messages only
• Verify the bot token is correct in config

If they can share the full error from the logs, that would help pinpoint the issue. The error message "Use Raw mode" suggests there might be a configuration option or mode toggle involved - is this coming from a specific tool or service they're using with Telegram?

@placid swallow — any chance you can share more context about when this error occurs? (e.g., what message type, media, or action triggered it?)

[little plaza]

hi hi

how do i re-enter my telegram bot code as it wasn’t working initially?

this is what i see now

[ocean venture]

This error is still a mystery — haven't found it in the Clawdbot codebase or docs.

To help debug, we need:

1. Gateway logs - Run clawdbot logs --follow and have them reproduce the error
2. Clawdbot version - clawdbot --version
3. Their config (sanitized) - Specifically the Telegram channel settings
4. What they were doing - Seems like they just said "hi hi" and got this error?

Questions:

• Is this happening to multiple users or just some?
• Is it in DMs or a group?
• Did this work before and suddenly stop?

Possible angles:

• "Raw mode" isn't in Clawdbot's Telegram code — could this be coming from a proxy, relay, or third-party tool?
• Are they using the official Bot API or MTProto (userbot)?

@versed wraith — any updates? If you have logs or version info, drop them here and we can dig deeper. 🦐

[little plaza]

how to i add my telegram bot id again? what do i type

as in the bot token in config

[ocean venture]

🛠️ Exec: grep -rn "schema" ~/clawd/clawdbot-ref/src/channels/plugins/telegram.ts 2>/dev/null | head -20

🛠️ Exec: grep -rn "Zod" ~/clawd/clawdbot-ref/src/channels/plugins/telegram.ts 2>/dev/null

[little plaza]

?

[ocean venture]

🛠️ Exec: grep -rn "schema node\|schema\|Unsupported" ~/clawd/clawdbot-ref/src/channels/plugins/ 2>/dev/null | head -30

🔎 Web Search: "Unsupported schema node" Zod error

🔎 Web Search: "Unsupported schema node" telegram bot api

🛠️ Exec: cd ~/clawd/clawdbot-ref && git log --all --oneline | grep -i "schema\|telegram" | head -20

🔎 Web Search: "Use Raw mode" telegram grammY error

That image context helps! The error is happening when processing a queued image message.

However, I can't find this error anywhere in the Clawdbot codebase, Telegram Bot API docs, or grammY library. "Unsupported schema node. Use Raw mode" isn't a known error from any of those.

We need more info:

1. Full stack trace from clawdbot logs --follow when the error occurs
2. Version: clawdbot --version
3. Any custom extensions or tools they're using?
4. Is this a fresh install or did it work before?

Quick questions for @versed wraith:

• Is this the first time using Telegram channel?
• Are you using any extensions or custom tools?
• Does it work with text-only messages (no images)?
• What model are you using?

If they can paste the actual stack trace from the logs, we can trace exactly where this error originates. The "Use Raw mode" hint suggests there's a schema validation somewhere that's rejecting the message format.

[covert schooner]

I had this same problem

[little plaza]

have you fixed it yet! @covert schooner

sadly my telegram is not connecting

[ocean venture]

To add your Telegram bot:

1. Chat with @BotFather on Telegram
2. Type /newbot to create a new bot (or /mybots to select an existing one)
3. Copy the token (looks like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11)

Then add it to Clawdbot:

Option A - Environment variable:

export TELEGRAM_BOT_TOKEN="your:token_here"

Option B - Config file (~/.clawdbot/config.json5):

{

[ocean venture]

Marcus, you're our hero! 🎉

What was the fix for you? Did you:

• Update Clawdbot version?
• Change some config?
• Disable a specific feature or extension?

Any details would help us solve this for everyone! 🦐

  channels: {
    telegram: {
      enabled: true,
      botToken: "your:token_here",
      dmPolicy: "pairing"
    }
  }
}

Then restart the gateway:

clawdbot gateway restart

The token is what you need — not a "bot ID". The token both identifies and authenticates the bot. 📎 https://docs.clawd.bot/channels/telegram

[ocean venture]

@covert schooner — @versed wraith is asking! What fixed it for you? 🦐

[ocean venture]

Got it — Marcus hasn't fixed it yet either. This error is happening to multiple users.

We need to escalate this. Key info we need:

1. Version: clawdbot --version (from anyone experiencing this)
2. Full error trace: clawdbot logs --follow when the error occurs
3. Config: Your Telegram channel config (sanitized)

@versed wraith @covert schooner — can either of you run:

clawdbot --version
clawdbot channels status --probe

And paste the output? This error isn't in the codebase we've searched, so it might be:

• A version-specific bug
• A configuration issue

• Related to how messages/media are being processed

If you have logs with the full stack trace, that's gold. 🦐

[little plaza]

yeah no still doesn’t work

[ocean venture]

Let's dig deeper — this error must come from somewhere.

[sinful thicket]

I have this issue as well. @covert schooner how did you fix it?

[ocean venture]

🎯 FOUND IT!

This is NOT a Telegram bug — it's a Web UI issue!

There's an open issue (#1749) about this exact error in the Web UI's Nodes/Accounts section:

Web UI: 'Unsupported schema node' error in Nodes/Accounts section

The Clawdbot web UI control panel shows an error when viewing the Nodes section:
"Accounts Unsupported schema node. Use Raw mode."

This is a UI rendering issue only — your Telegram bot still works!

Workaround:

• Click "Use Raw mode" in the Web UI and it works fine
• The error is cosmetic, not functional

Fix coming: The team is aware and working on it.

@versed wraith @covert schooner @sinful thicket — you can ignore this error for now! It doesn't affect Telegram messaging. 🦐

[little plaza]

how to use raw mode