Bot Cookbook

Search the index

Search templates, recipes, and prompts.

Updated 18 Oct 2026

When your bot gets it wrong

When the result is off, say what is wrong and what you wanted instead. Put a rule that should last into the description, and correct a stale fact in the chat. If it stopped, look for a card that says why.

  1. 01

    Ask for a revision

    Say what is missing or messy instead of sending a bare retry. The get-started guide expects you to name the fix so the bot knows what good looks like.

    Get started

  2. 02

    Put lasting rules in the description

    If the mistake is a rule you want every time, add it to the description. If it is only about this task, say it in the message. That split is how the bots page separates standing rules from today's work.

    Create and manage Bots · Write the instructions

  3. 03

    Correct a stale fact out loud

    Memory helps the bot keep a role. It is not a source of truth. Fix wrong assumptions in the chat, and ask for fresh citations when the decision matters.

    Create and manage Bots

  4. 04

    Read the card if it stopped

    Usage caps, rate limits, and timeouts show up as cards that explain the block. Unattended approvals can also time out and show Expired without running the action.

    Grok Bot changelog · Approvals, security, and privacy

Questions

Should I delete the bot when it is wrong?
Not for one bad answer. Say what to change. Delete removes the bot's profile, conversation, and routines. The bots page says to hide it instead if you may need the work later.
Will it remember the correction?
A correction in the chat fixes that assumption. A rule you want every time belongs in the description. Memory is still not a substitute for the original file or app.
What if a website changed and a routine broke?
Run the skill again after a site, connector, or file layout changes, and pause the routine when its inputs or steps change.

Sources