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