抄作业 / 做成了什么 / Grok Bot
Forum: one Bot stuck on "failed to respond" because of its chat history
标题与摘要为原文,未翻译。
- 做了什么
- Report of a primary Bot that stopped replying while other Bots on the same computer worked; staff found the model provider's safety filter was flagging security-related content in that Bot's conversation history, so every reply sent with that history was refused.
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体来源未提供
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出,本站不补写。
- 来源原文摘录
Where does the bug appear (feature/product)? Grok Bot Describe the Bug My primary bot (“Grok Bot”, id e1f88b48-0a35-4a45-9d37-9065ec52900e) stopped replying on Oct 8, 2026. Other bots on the same account and the same Agent Computer reply normally (a bot created at 19:27 MSK the same evening works fine), so this looks like a stuck runner for this one bot, not the computer or usage. Timeline (UTC+3): • ~19:00 last normal reply; the bot was working on a long background task • 19:06 my next message got no reply, the bot showed “working on it” indefinitely • 19:24 chat shows “A background task was
展开全文
stopped after 50 minutes so it would not hang” • since then every message fails with “Bot failed to respond / Something went wrong while generating the reply. Try again.” Already tried: • Fully quit and reopened the app • Rebooted the Mac …RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖,照录原文,未翻译。
- 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文:forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次,再决定频率
- 风险与限制
- 作者的结果不保证能复现,以原帖为准
- 用量预估
- 用金属计算器估一下