Your 8am automation didn't run. Your laptop was asleep. This one came up in a li
By Jaspinall · November 13, 2026 · Curated by George's Blog
Your 8am automation didn't run.
Your laptop was asleep.
This one came up in a live session I ran. Someone builds a morning report, a price check or an inbox sweep. It works great for a week. Then one Monday the report just isn't there.
Nothing broke. The job was scheduled on their own computer, and the lid was closed.
Local automations only fire while the machine is on and awake. Sleep, a dead battery, a restart for an update, and that 8am job gets skipped. Some schedulers catch up when you open the lid. Others never run it at all. Either way, the report that was supposed to be waiting for you shows up late or not at all.
The fix isn't a better script. It's moving the job somewhere that never sleeps.
That's what cloud routines are for. In Grok Bot, a routine is a saved prompt that runs on a schedule on a server, not on your laptop. Close the lid, fly to a trade show, leave the computer off all weekend. The 8am brief still lands at 8.
You don't have to move everything though. Run each automation through three questions.
If it has to land by a set time?
⤷ Cloud. Morning reports, price checks, anything someone reads first thing.
If it needs files or apps that only live on your computer?
⤷ Keep it local, and run it while you're actually at the desk.
If nobody would notice it was a day late?
⤷ Either works. Pick whatever is cheaper to run.
Then check the clock. A server still needs to know your time zone. A 6am job set in UTC fires at 1am in New York. Say the time zone out loud when you set it up.
One more habit worth stealing. Have the job tell you when it fails, not just when it works. A silent miss costs you more than a loud one.
The image below uses example data.
Open your list of automations this week. Anything with a time in its name probably belongs in the cloud.
🪿