heartbeat caused session to orphan and start new

- Jan 18, 2026 - Active conversation about OAuth implementation
- Last user message: 00:16 UTC
- Last bot message before failure: 00:19 UTC
- According to logs heartbeat ran as expected at 01:03 and 02:03 UTC
- 03:03 UTC: No heartbeat logged - something failed
- 04:03 UTC: Brand new session created for no apparent reason
- User message at 07:40 UTC - agent has zero memory of prior work, is operating in a fresh session.

From user perspective: Same continuous Telegram chat, no messages between 00:19 UTC - 07:40 UTC
From agent perspective: Completely new session, no context

Evidence:
1. Old session file still exists: 8346c347-014d-4942-a4b2-95bd22048fc0.jsonl (398K, last activity 02:03 UTC)
2. New session created: 2fdfd71e-abe1-4eef-ac90-269044f5b0b3.jsonl (created 04:03 UTC)
3. Old session is NOT in sessions.json registry - orphaned but file exists on disk

Heart Config at failure:
"heartbeat": {
  "every": "60m",
  "target": "last"
}


Version: clawdbot 2026.1.16-2
Host: Debian 12
Gateway: Running since earlier Jan 17, no restart

Question: Is this a known issue with heartbeat? What causes sessions to get orphaned?

Question: Is this a known issue with heartbeat? What causes sessions to get orphaned? What is the best way to mitigate this? Is it possible to fix/restore the old session?
Was this page helpful?