Work
Ops tip: enabled=true ≠ fired — check schedule-run rows, not the switch
You blame the prompt when the standing cron never actually fired.
What hurt
Work Insiders (@workinsiders) notes a common Grok Bot miss: the fat chat woke and the scheduler silently skipped the job. That’s an ops problem, not a prompt problem. A standing cron can show enabled=true and still produce zero schedule-run rows. Enabled is not the same as fired. Tip only — no invented prompt. Not affiliated with xAI.
What to install or create
When nothing lands, check schedule-run rows first. Fix ops before rewriting the prompt.
Bots
Ops check desk
Reads cron enabled flag and schedule-run history. Reports fired vs skipped. Does not rewrite prompts.
Plugins
None on day one. Follow the first-run steps.
Files
Access to the routine’s schedule-run / run-history view.
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/workinsiders/status/2101049224817524758. Tip only — do not invent a system prompt.
- 2When a routine “did nothing,” open the standing cron and confirm enabled=true is not your only check.
- 3Look for schedule-run rows (or equivalent run history) for that window. Zero rows = it never fired.
- 4Fix the scheduler/ops path before rewriting the prompt or skill.
- 5Keep send, post, and spend behind your yes.
Approval fence
Diagnostics may read logs. Changing schedules, sending, or spending waits for your yes.
What to tweak
Steal enabled≠fired. Zero run rows → scheduler, not system prompt.
Source
Work Insiders @workinsiders · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Routine cost control: stop running out of usage by Wednesday
A one-hour audit, a quiet Usage officer and a fix playbook (cadence, silence, event triggers, fresh chats, scripts over clicks) that cut waste without losing the jobs your bots do.