Hey @TG_Promo, thanks for the detailed report and the timestamps.
What you’re seeing is the computer going to sleep. A few minutes after the app disconnects and no bot is working on it, the computer is paused. Processes running inside it (like nohup loops) don’t count as activity, so they stay frozen until the next wake. That is why the gaps run from minutes to hours. Your freeze windows line up with that. This is a known issue for long-running jobs, and I’ve added your report to it.
The restart on Oct 10 was an automatic computer update. Files carry over through an update, but running processes don’t, which is why your scripts were gone.
For now, a few things help:
- Keep the Grok Bot app open and connected while the pipeline needs to run. The computer woke each time your app reconnected.
- Have each collector run catch up on the time since its last successful run (keep a timestamp in a file), so a missed tick doesn’t lose data.
- Have your publishing routine check whether your scripts are running and start them if they aren’t, so they come back after an update.
On the approval cards: the Auto-review safety check can fail to complete, and when that happens it asks for approval even if an allow rule matches. That part is a separate issue we’re tracking.