Fix a Grok Bot routine that queues late or finishes silently

A scheduled routine can look dead while the slot already fired. Cursor staff (Colin, Sep 2, 2026) reported two platform issues: runs sit in a queue for about 10–37 minutes after the set time, and some runs finish without posting a chat message. For a routine that never starts at all, use Fix a Grok Bot routine that did not run. For Sentry issueCreated with empty lastRunAt, see Fix a Grok Bot Sentry issueCreated routine that never runs.

Read “Next run” correctly

Open the Bot → View conversation details → Routines, then open the routine.

1. Confirm it is enabled, the schedule and time zone match the slot you expected, and the owning Bot still exists.
2. Watch Next run. When it shows Run now after the scheduled time, staff say the slot is due and the run is still queued.
3. Wait through the queue window (staff examples: start ~9–37 minutes after the slot). Check recent run history for a start or finish timestamp.
4. Skip delete-and-recreate as a fix for a late start. Staff said recreation does not clear the queue delay.

Editing Bot instructions does not change the routine schedule. The platform you used to create the routine (desktop or iOS) also does not matter for this issue.

When chat stays quiet after a run

Staff’s second known issue: the run can execute and still leave no message in the conversation. File-writing routines look healthy because you see the file; chat-only check-ins look empty even when history shows success.

1. Open the same Routines panel and inspect run history for success or failure after the scheduled slot.
2. Prefer a routine outcome you can verify outside chat — a file write, a ticket comment, or another durable artifact — while the silent-finish bug is open.
3. For an on-demand check-in right now, send a message in the Bot chat. Staff called that the reliable path while queue delay and silent finish remain tracked.

Docs checklist still applies

Official troubleshooting for a miss still asks you to verify: enabled, schedule and time zone, owning Bot exists, required plugins authenticated, computer can reach the source, usage or account access not paused. Event listeners need a valid channel, repository, or matching rule. Use Test run only with safe input; testing performs real external actions.

Pitfalls

• A 10–20 minute start delay can show up on healthy routines too; treat multi-dozen-minute waits plus Run now as the queued state staff described.
• Recreating routines does not fix platform queue delay.
• Empty chat after a successful history row is the silent-finish issue, separate from a schedule that never fired.