Evidence record / openclaw

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-24-openclaw-stable-rejects-old-telegram-imports-instead-of-replaying-them-as-fresh-work

Stable rejects old Telegram imports instead of replaying them as fresh work. The October importer takes the oldest usable received/message timestamp and marks legacy work older than 24 hours failed with stale-legacy-import. It preserves legacy source evidence rather than turning stale owner instructions into a new actionable queue item. The implementation explicitly does not sweep work already imported into the current queue.

Channel: tagged-release. Half: defect. Date: 2026-10-18.

Operator consequence: Use 10.7 before legacy Telegram recovery, then inspect migration warnings and pending work. A genuinely unprocessed old instruction will also be withheld; the owner must decide whether to issue it again. The fix removes automatic replay, not the need to review recovery intent. Do not describe it as a queue cleanup or infer 9.33 behavior merely from a missing October filename.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-openclaw-stable-rejects-old-telegram-imports-instead-of-replaying-them-as-fresh-work

Profile citations

  • OpenClaw / claim / telegram-import-rejection-stable
  • OpenClaw / posture / governance

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact