抄作业 / 做成了什么 / Grok Bot

做了什么

Bug report: three scheduled Grok Bot routines failed with only "Activity task failed" and no reason, while a manual rerun on the same healthy box succeeded.

场景

周报 / 简报 盯 PR / 仓库 日程会议

资料完整度

• ✓ 作者与原链接有
• ✓ 做了什么有
• ✓ 来源原文摘录有
• — 截图 / 媒体来源未提供
• — 步骤 / 章节来源未提供
• — 提示词 / 配置原文来源未提供
• — 结果 / 数字来源未提供
• ✓ 风险提示有
• ✓ 相关条目有

— 表示来源没有给出，本站不补写。

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug On Oct 2, three Grok Bot scheduled routines on my account failed with only “Activity task failed” (6:50 PM, 7:00 PM and 8:05 PM ET, on different agents). The box looked healthy at those times: no host restarts, normal CPU, free disk, and a manual rerun of one routine on the same box succeeded a little later. Run records aren’t on the box, so I can’t see why they failed. Questions: • Where can I see the real failure reason for a routine run? • Is there an automatic retry for “Activity task failed”? • Feature request: rotate

展开全文

the box telemetry log instead of stopping at its size cap, and add timestamps to its lines. • Feature request: swap or more RAM on the box. Chrome renderers get OOM-killed regularly with 16 GB and no swap. Steps to Reproduce Schedule Grok Bot routines and let them run. Expected Behavior …

摘自论坛首帖，照录原文，未翻译。

提示词

来源没有给出可直接复制的提示词原文。

怎么复制

1. 读原文：forum.cursor.com ↗
2. 把原文里的步骤/提示词整理成一条消息交给 Bot
3. 先手动跑一次，再决定频率

风险与限制

• 用到浏览器或网页登录：最耗额度，能用 connector 就别开浏览器
• 定时运行会持续消耗额度：频率从低开始，跑稳再加
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下