Grok Bot Bot's computer paused by the host for 9.5 h overnight (no crash inside the VM), plus repeated 5–120 min pauses

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Hi, my Grok Bot computer is being paused from outside the VM, overnight and repeatedly during the day. Nothing inside the box crashes. I collected evidence before touching anything; I have not run Reset, Recover or Update.

Plan / app: SuperGrok Plus, Mac desktop app, 12 Bots on one computer
Computer: grok-bot-vm-416470035, last boot 2026-10-19 08:56 UTC, no reboot since
Resources are fine: 15 GiB RAM with no OOM or hung-task messages in dmesg and cgroup memory.events all 0; disk 125 GB at 14%; load near 0
Main pause: 2026-10-20 17:18 UTC → 2026-10-21 02:51 UTC (about 9h32m). Three independent processes stopped logging within seconds of each other and resumed within about 2 minutes of each other:

WhatsApp sync daemon: last line 17:18:24, next 02:53:20 UTC
a 2-minute board watchdog: last tick 17:18:18, next 02:52:07 UTC
rclone mount: silent from about 17:15, resumed 02:50:44 UTC with context canceled / Device or resource busy errors
Our monotonic-vs-wall-clock check recorded “frozen 34308s”. Cron stopped ticking for the whole window.

Shorter pauses (UTC): 10-20 15:01 (56 min), 17:01 (117 min); 10-21 02:23–04:18 (57 min), 05:08 (20 min), 05:45 (20 min), 06:12 (14 min), 06:51 (47 min), 07:40 (9 min), 07:57 (4 min).

My Mac stayed awake all night (pmset shows no sleep), so this isn’t the desktop app disconnecting.

Questions:

Is this computer being suspended or live-migrated by the host? Is it related to the 10-17 account/computer move?
Can it be kept running 24/7? Bots need it live overnight.
Is there anything I should do (or avoid) on my side?
Thanks.

Steps to Reproduce

It happens automatically and without warning.

Expected Behavior

Computer and associated jobs should continue running all night.

Operating System

MacOS

Version Information

Version: 0.72.0
Built: 2026-10-18T04:33:44.546Z
Release Track: stable
OS: darwin

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

6

Hey @Philip_Walton,

Thanks for the detailed timeline, it made this easy to trace. Yes, those pauses are the computer going to sleep, and it’s expected behavior rather than a fault. When no Bot is working on it and no app is actively using it, the computer is paused a few minutes later with its memory and disk saved, then resumes exactly where it left off the next time something needs it. Programs running inside the computer (your WhatsApp sync, the watchdog, the rclone mount and cron) don’t count as activity, so they freeze along with it. That’s why nothing crashed, there was no reboot, and the clock jumped.

Your timeline matches this. On Oct 20 the computer went to sleep at about 17:15 UTC and stayed asleep until about 02:50 UTC, when one of your daily scheduled Bots was due and woke it. The shorter pauses follow the same cycle: it wakes for a scheduled run, a message or opening the app, then goes back to sleep a few minutes after the work ends. Keeping your Mac awake generally doesn’t change this, because an open app on an unattended Mac doesn’t count as active use.

It isn’t related to the Oct 17 move: the computer slept the same way before and after it. The overnight gaps likely got longer from Oct 19 because there were fewer scheduled Bot runs overnight to wake it.

There’s no way to keep the computer running 24/7 today. Keeping it awake while background work runs is something the team is looking at. In the meantime:

  • Move overnight work into scheduled Bots rather than cron jobs or daemons inside the computer. Each scheduled run wakes the computer, does its work, and lets it sleep afterwards.
  • For anything that has to survive a pause, make it resume cleanly: on wake, check how much time has passed and catch up, and have the rclone mount and other long-lived connections reconnect, since network connections drop while the computer sleeps.
  • A command a Bot starts in its own shell should keep the computer awake for a while (up to about 30 minutes), which can cover short jobs but not an all-night process.

There’s no need to Reset, Recover or Update. None of them change this behavior.

This is the same situation as this earlier thread, if you’d like to follow along there.

8

Thank you for the thourough explination. That helps me rethink how I’m using my Grok Bot setup.

9

I’ve also had the issue where my grokbot’s computer was getting sent into sleep overnight and multiple times during the day, interfering with processes i’m running. This issue seems to have gotten worse from last week to this week. I have just updated from the old 100/usd month plan to the 200/usd month plan. Is there a plan to make it possible to have the grokbot computer run 24/7, or at least set times that it is not allowed to go to sleep?