← View index

Discord meal-log silence RCA — 2026-05-26

過去レポートのView/ソース規律バックフィルで生成したView。

What happened

Root cause

The user message landed during a Gateway restart boundary. The transcript retained the user message, but the normal assistant turn did not produce a response. The post-check watchdog only verified Gateway health and posted a cron/direct-delivery status message. That status message appeared after the user prompt but was not a real answer, and the recovery logic treated health recovery as enough.

The earlier explanation that nutrition lookup/tool work caused the wait was wrong. The local food DB work and View render take sub-second to a few seconds once a live turn is actually running.

Fix applied

- Scans owner Discord transcripts.

- Treats cron/direct-delivery mirror messages and "OpenClaw見守り" as non-answers.

- Flags stale user prompts that have no real assistant text after them.

Verification

The full test_openclaw_watchdog.py run hit the live watchdog lock in this running environment, so I did not count that as a clean full-suite pass.

質問したい箇所を選択
この箇所について質問
✓ 質問を送信しました