Private beta is open Request yours
gramflow
Get access

Troubleshooting

The snags people hit first, and how to clear them.

My bot doesn't reply

Work down this list — it's almost always one of these:

  • Is it deployed? Your live bot only runs what you've deployed. Open the bot's Flows page: if the status line says Not live or Not live yet, press Deploy bot.
  • Does the flow start with a trigger? Every flow needs a Message Received or Command Received node at the top — nothing runs without one.
  • Does the trigger match? A Command Received for /start won't fire on plain text, and a Message Received with a text filter ignores photos. Message flows also skip /commands unless you turn off Ignore commands.
  • Is another flow answering first? Flows are checked top to bottom and the first match wins. See the next section.
  • Is the token still valid? If you regenerated the token in BotFather, the old one stops working — reconnect the bot with the new token.

The wrong flow answers

Gramflow checks your flows from the top of the Flows page and the first one that matches answers (how matching works). If a flow shows Never reached, a flow above it already handles those messages: press Move above it, or narrow the flow above (for example, a text filter instead of any message). Use Test all to send real messages and see which flow handles each one.

Run is greyed out

A flow with errors can't run. Hover Run to see why, or open Checks in the builder header and use Show node to jump to what needs fixing. If Run says Test all is running, a Test all session on the Flows page is using your test bot: stop it there first.

"Invalid token" when connecting

Copy the token straight from @BotFather — it's the whole line after "Use this token", in the form 123456789:AA…. Don't include the surrounding text or a trailing space. If it still fails, send BotFather /revoke to mint a fresh token and try again.

TEST works but LIVE doesn't (or vice-versa)

TEST and LIVE are separate environments. Changes you make on the canvas run in TEST until you deploy them; LIVE keeps running the last release you deployed. If a fix works in TEST but users still see the old behaviour, press Deploy bot again. If a deploy made things worse, open History and roll back to the release before it.

The Generate Text node errors or does nothing

AI nodes use your own model key (bring-your-own-key). Add a key for OpenAI, Anthropic, or Google in your bot's settings, and make sure the node is pointed at a model that key can access. A missing or unauthorized key is the usual cause.

Replies are delayed or dropped under load

Gramflow rate-limits each bot to protect it from bursts. Telegram automatically redelivers any update that was throttled, so messages aren't lost — they arrive a moment later. If you're consistently hitting the limit, simplify the flow or space out whatever is driving the traffic.

Still stuck?

Ask in the Telegram channel — during the beta we answer there directly.