When your bot gets stuck: simple fixes for common problems Explainer

4 min read

Sometimes a bot misunderstands, can't reach an app, or seems to stop. Most of the time the fix takes a minute. Here's what to try first, in plain language.

The short version

When something goes wrong, start in the same chat and ask the bot what happened. It can usually tell you what it tried, where it got stuck and what it needs from you. Most problems come down to a few causes: the request wasn't clear, an app connection needs signing in again, the bot is waiting for your OK, or a website needs a person for one step.

Step one: ask the bot

Bots keep the conversation in mind, so you don't need to start over. A plain question works: "That didn't work. What happened, and what did you try?" The answer often points straight at the fix, like a missing connection or a detail it couldn't find. Don't just send the same request again and again; if it failed once for a reason, it will usually fail the same way.

The answer misses the point

If the result is close but wrong, the request probably left room to guess. Reply with what to change: "Only this week's orders", "shorter", "as a table". If it's far off, say the goal again in a sentence and add the details it couldn't know. See How to write a request your bot gets right the first time.

It says it can't reach an app

A bot works with apps like email or calendars through connectors. If a connector was never added, or its sign-in has expired, the bot can't get in. Ask it: "Check whether my Google Calendar connection is working." If it needs you to sign in again, it shows a connect card with an Authorize button. Click it and sign in on the app's own page. You never type the password into the chat. More in Connecting apps.

It seems to be waiting

Often a bot hasn't stopped at all; it's waiting for you. Look back up the chat for:

See Safety and approvals.

A website task is stuck

When a bot works on a website, it uses its own browser on a cloud computer, and you can watch it live. Open the bot's info pane by clicking its name in the chat header, and look at the preview of its screen. If it's stuck on a sign-in or a check only a person can do, open the full view and click Take control to finish that step yourself. See Your bot's computer and browser.

A routine didn't run, or ran at the wrong time

Open the bot's info pane and check its Routines list. A routine that's switched off says "Paused". If it ran at an odd hour, the time zone may be off: ask the bot, "Show me when my morning summary routine runs, and in what time zone." You can fix the time just by asking. See Routines.

The bot's computer is acting up

If the bot reports that its computer won't respond, ask it what it found first. If that doesn't clear it up, Settings has an Update Bot's Computer option on the Computer tab. It moves the bot to a fresh cloud computer and keeps files and logins, though installed software has to be reinstalled. It asks you to click twice to confirm. This is a repair tool, not something to run for new features. More in Keeping Grok Bot up to date.

The app itself looks odd

If buttons or pages look wrong, especially right after an update, fully quit the app and open it again. That clears most display problems.

What not to do

Still stuck?

Check Cursor's official Grok Bot documentation, since apps change over time. Then try the job again in smaller steps; a small step that works tells you more than a big one that doesn't.

Ideas to try

  • Finding out what went wrong.
    That didn't work. Tell me what you tried, where it stopped and what you need from me to finish.
  • Checking an app connection.
    Check whether my Gmail connection is working. If I need to sign in again, show me how.
  • Fixing a routine that ran at the wrong time.
    Show me when my morning summary routine runs and in what time zone, and change it to 7 AM Central time on weekdays.