Pause or delete a Grok Bot routine

Stop a Grok Bot routine from firing when usage is climbing, a trigger is too broad, or the job is obsolete, without tearing down the Bot that owns it. Official Routines shows the desktop switch on each routine row for pause or resume, the Pause or Resume button inside the routine, and Delete routine (trash icon) with a confirmation that stops future runs and cannot be undone. On the phone, turn off Active to pause, or swipe the routine row to delete. Deleting a Bot also removes its routines; hiding a Bot from the sidebar does not pause them. Routines run in the cloud while your laptop is closed, so an Active schedule or trigger can keep spending usage after you walk away.

What you need

Desktop or phone access to the Bot that owns the routine, and a decision between a temporary pause and a permanent delete. Pause when you will resume after a source change or a usage scare. Delete when the instruction is obsolete and you do not want the row to return. Confirm schedules and triggers first with Set a schedule on a Grok Bot routine or Set a Slack listener on a Grok Bot routine so you know why it was firing. For a live check before you resume, use Test a Grok Bot routine. More Bot jobs sit on the Grok Bot hub.

Pause or resume on desktop and phone

1. On desktop, click the Bot's name at the top of the chat to open its details, choose Tasks, and find the routine under Routines. Each row shows the name and when it runs, or Paused.
2. Flip the switch on the row to pause or resume, or open the routine and use the Pause or Resume button at the bottom.
3. On the phone, open the Bot's profile, open the routine, and turn Active off to pause or on to resume.
4. Confirm the row shows Paused (desktop) or Active off (phone) before you leave. A paused routine stays saved and spends no schedule or trigger runs until you resume it.

After a long stretch away, Grok Bot may ask whether to keep routines running and pause them if you do not respond. Re-open Routines when you return and confirm the ones you still want. A Bot can own up to 50 routines, and Run history keeps the 20 most recent runs for each.

Delete a routine

1. On desktop, open the routine from Routines, then choose Delete routine (trash icon). Confirm the prompt — deletion stops future runs and cannot be undone.
2. On the phone, swipe the routine's row to delete, then confirm if the app asks.
3. If the whole Bot should go away, delete the Bot instead; that removes routines owned by that Bot. Prefer hide from the sidebar only when you still want routines to keep running.

Copy a request ID from a failed run (right-click the run → Copy request ID) before you delete if you still need it for support. Deleting the routine does not wipe shared computer files or browser sessions on the Bot computer.

Pitfalls

Hiding the Bot from the sidebar while leaving routines Active keeps cloud fires running and spending usage. Deleting when you only needed a pause removes the instruction with no undo. Resuming a broad Slack or webhook trigger without narrowing it first can burn a week of usage in a day. Assuming a paused routine will catch up missed schedule slots fails — after resume it waits for the next matching time or trigger.