Trabajo
Ops tip: enabled=true ≠ fired — check schedule-run rows, not the switch
You blame the prompt when the standing cron never actually fired.
Qué dolía
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.
Qué instalar o crear
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
Ninguno el primer día. Sigue los pasos del primer uso.
Archivos
Access to the routine’s schedule-run / run-history view.
Rutinas
Ninguna en el primer uso. Mira primero una pasada manual.
El prompt
Esto es un consejo, no un prompt de sistema para pegar. El autor no publicó uno. Sigue los pasos del primer uso.
Primer uso
- 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.
Valla de aprobación
Diagnostics may read logs. Changing schedules, sending, or spending waits for your yes.
Qué ajustar
Steal enabled≠fired. Zero run rows → scheduler, not system prompt.
Fuente
Work Insiders @workinsiders · Publicación original
Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.
Paquete Pro
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.