Productivity · Developers · Emerging

Scheduled routines for Grok Bot are not firing as expected, indicating a potential server-side scheduler fault

Grok Bot routines failed to execute at scheduled times due to a bug, affecting automation.

Who experiences it: Developers

Momentum

0%

Pain

75

Competition

0

Opportunity

62/100

Signals over time

2 observed signals across 1 sources, tracked for 6 days. Confidence: low.

What people are saying Observed

  • “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 k”

    RSS Feeds · complaint

  • “All grok bot routines failed to run. Where does the bug appear (feature/product)? Grok Bot Describe the Bug Scheduled routines stopped firing for all my bots on Thu 8 Oct 2026. Inbox’s scans (every :29 and :59, 08:29 to 20:59 UK) ran until about 14:00, failed at 16:55, and haven’t run since, even after I paused and resumed the routine. Another 16:15 routine also failed, and a one-off routine set for 18:06 never fired. The bots work normally when I message them, so it looks like a server-side scheduler fault Steps to Reproduce All grok bot routines failed to fire at the scheduled times Expected Behavior Routines run at scheduled times Screenshots / Screen Recordings Operating System MacOS iOS Version Information Grok Bot 1.14.0 (17267) · runtime e9651e08edc0248a43ce2d13839fa55c7d2e1425 · embedded bundle · channel production Additional Information Paused and Resumed, created a copy of the routine instead both failed to solve the issue Does this stop you from using Cursor No - Cursor works, but with this issue 1 post - 1 participant Read full topic”

    RSS Feeds · complaint

Why now? AI inference

Existing solutions Observed

    See the full evidence, competitor gap matrix and opportunity report.

    Free account. No credit card.