抄作业 / 警告 / Grok Bot
Grok Bot routines don't auto-run on schedule
标题与摘要为原文,未翻译。
- 做了什么
- Staff (Colin): Editing bot instructions or which platform created a routine does not break schedules — late “Next run: Run now” usually means the slot fired but sat in a queue (often 10–37 min), and some runs finish without posting to chat; don’t recreate routines; message the bot for an on-demand check-in.
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体有
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出,本站不补写。
- 来源原文摘录
Where does the bug appear (feature/product)? Grok Bot Describe the Bug Platform: iOS app (monitoring); affected bot originally created on Windows 11 desktop app, instructions edited via desktop multiple times since. Summary: Multiple scheduled routines on one Grok Bot fail to auto-execute at their set time. This has happened repeatedly across several days, including after deleting and recreating the routines. A separate routine on a different bot (same account) runs normally every day without issue. Two possible contributing factors are described below (routine creation platform, and frequency
展开全文
of instruction edits) — neither is confirmed as the root cause. Expected behavior: Routine should start automatically at the scheduled time (e.g., 11:00 KST, 21:00 KST) without requiring the user to open the app or send a manual message. Actual behavior (timeline): …RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖,照录原文,未翻译。
- 效果截图

截图来自原帖 - 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文:forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次,再决定频率
- 风险与限制
- 这是一条额度/故障反馈(警告),不是可复制的作业。
- 有删除、退订或取消动作:先出清单,逐项确认再执行
- 定时运行会持续消耗额度:频率从低开始,跑稳再加
- 作者的结果不保证能复现,以原帖为准
- 用量预估
- 用金属计算器估一下