Grok Bot routines failing or running hours late across several bots since ~10:20 AM ET Oct 8

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Since about 10:20 AM ET on Oct 8, 2026, scheduled routines on our account have been failing, getting skipped, or running very late across several different bots, all on one shared computer.

What we see:

  • A routine set to run every 5 minutes during market hours only completed a handful of times all day, with gaps of 1.5 to 2 hours and some runs marked failed.
  • Several other routines (hourly, midday, afternoon, and after-close) fired 1 to 2 hours late and then failed before doing any work, or never started at all.
  • A few did run, just 60 to 70 minutes late, so the scheduler looks backlogged rather than completely down. It’s still happening after 5 PM ET.

What we ruled out:

  • The routines haven’t changed and their schedules are correct.
  • Runs that do fire finish in 1 to 3 minutes, so this isn’t overlap.
  • The shared computer is healthy: low load, plenty of free memory, no pressure.
  • Weekly usage is around a third, nowhere near the limit.
  • Messages between bots still wake them right away. Only scheduled runs are affected.

Is this a known incident, and is there anything on our side that would help routines catch up? Some of our routines watch time-sensitive things, so even a status note would be useful. We also sent this through in-app feedback.

— Tech Support

Steps to Reproduce

No single reproducible step; this is a scheduling/timing problem. Scheduled routines have been late, skipped, or failing since about 10:20 AM ET on Oct 8, 2026 across several bots on one shared computer. Details are in the description above.

Operating System

Other

Version Information

Not provided by reporter (Grok Bot, shared computer). Version info to be added on request.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Capital_EyeMotors, thanks for the detailed write-up, and for ruling out the usual suspects before posting. That made this quick to match up.

Yes, this is a known issue we’re tracking. Since around 10 AM ET on Oct 8, scheduled Grok Bot routines have been held back, running late, or getting marked as failed. It isn’t caused by anything in your setup, your shared computer, or your usage. Messages to and between bots aren’t affected, which matches what you’re seeing.

Short-interval routines like your 5-minute one show the biggest gaps right now. While one run is waiting to go through, the next scheduled slots are skipped rather than stacked up, which is why you’re seeing 1.5 to 2 hour gaps instead of a steady backlog.

In the meantime:

  • Leave your routines enabled. Pausing, resuming, editing the schedule, or recreating them won’t help here.
  • For anything time-sensitive, message the bot directly and ask it to run that task now. Direct messages are still going through right away.
  • Runs missed during this window won’t be replayed automatically.

There’s no timeline to share yet, but I’ll post here as soon as routines are running normally again.