Pause, edit, or delete a Grok Automation

Open a saved Automation when you need to stop scheduled runs, change the brief, or remove it entirely. Official Automations in Grok states that any automation can be paused, resumed, edited, or deleted at any time, and that every run is a full conversation you can reopen from run history.

Automations live on grok.com and in the Grok iOS and Android apps. They are consumer Grok jobs, separate from Grok Bot routines on the Bot computer. For creating the first one, see Create a scheduled Grok Automation or Start a Grok Automation from chat.

Open the Automation

1. Go to grok.com/automations while signed in, or open Automations in the Grok mobile app.
2. Select the Automation by name.
3. Review the saved instructions, schedule or email trigger, connectors, skills, and report channel before you change anything.

If you built it from a chat message, still open the Automations page so you edit the saved job rather than a one-off follow-up in an old thread. Every future run is a fresh request with the same instructions and current data.

Pause and resume

Pause when the source system is changing, you are traveling without wanting morning briefs, or a bad prompt is about to fire again. Resume when the brief and connectors are ready. Pausing stops new scheduled or triggered runs; it does not delete run history. Existing run conversations stay available so you can read what already happened.

Use Run now after you resume if you want a live check before the next scheduled fire.

Edit the job

Edit when the output format, sources, or cadence should change:

1. Update the instructions the way you would brief a coworker: what to check, what done looks like, and what to send you.
2. Adjust attachments, connectors, and skills only when the job still needs them. Type @ to mention a connector the job should use on every run.
3. Change the schedule (once, daily, weekdays, weekly, monthly, or yearly in your timezone) or the email-trigger filters (sender, recipient, or subject). Email triggers need SuperGrok; scheduled automations are available more broadly.
4. Set how it reports back: email, app notification, both, or neither.
5. Save, then Run now once so you see a real conversation in run history before you trust the next automatic fire.

Keep the output format inside the saved instructions. A chat follow-up after one run does not stick for later fires.

Delete

Delete when the job is obsolete or was created by mistake. Deletion removes the Automation from the list so it will not fire again. Open important run threads first if you still need the written results; treat delete as immediate for the schedule itself.

Pitfalls

• Editing only in an old run conversation — change the Automation on the Automations page so the next fire picks up the new brief.
• Leaving a vague brief after a pause — fix instructions before resume, or the first fire repeats the same weak output.
• Confusing Automations with Grok Bot routines — pause Bot routines inside the Bot's Routines panel; Automations are managed at grok.com/automations.
• Skipping Run now after a major edit — prompt and connector bugs show up cheapest on a manual run.