#New error in log

1 messages · Page 1 of 1 (latest)

velvet summit
#

I've updated to new version 2025.5.18 and have noticed a new error appearing in the logs, corresponding to telegram disconnecting, is this a known issue?

14:58:39
error
diagnostic
lane task error: lane=main durationMs=2454562 error="EmbeddedAttemptSessionTakeoverError: session file changed while embedded prompt lock was released: /home/admin/.openclaw/agents/lead-scout/sessions/b6b47e15-df80-4027-b1fb-7caea89dd67d.jsonl"
14:58:39
error
diagnostic
lane task error: lane=session:agent:lead-scout:telegram:direct:6938637819 durationMs=2454571 error="EmbeddedAttemptSessionTakeoverError: session file changed while embedded prompt lock was released: /home/admin/.openclaw/agents/lead-scout/sessions/b6b47e15-df80-4027-b1fb-7caea89dd67d.jsonl"
14:58:39
error
Embedded agent failed before reply: session file changed while embedded prompt lock was released: /home/admin/.openclaw/agents/lead-scout/sessions/b6b47e15-df80-4027-b1fb-7caea89dd67d.jsonl

surreal elmBOT
rugged hollyBOT
# velvet summit I've updated to new version 2025.5.18 and have noticed a new error appearing in ...

Yes, this one is known now: https://github.com/openclaw/openclaw/issues/84059

That exact EmbeddedAttemptSessionTakeoverError: session file changed while embedded prompt lock was released signature is being tracked as an open P1 session-state/message-loss regression around 2026.5.18. It is not necessarily Telegram-specific: Telegram is where you see it because the inbound Telegram turn is the one trying to run the embedded agent, then the agent fails before reply.

The useful distinction:

  • If the log also says Polling stall detected, getUpdates, 409 conflict, or network/fetch errors, that is Telegram polling/network territory. Docs: https://docs.openclaw.ai/channels/telegram#troubleshooting
  • If the main failure is this session-file lock error, it is the open embedded-runner/session issue above.

Short-term: restart may temporarily clear it, but /new may not reliably help for this specific bug. If you can, add your Telegram log excerpt + openclaw --version + whether it happens on every Telegram message or only after long-running replies to issue #84059. That gives maintainers a second channel repro instead of only the Feishu report.

For the general debug bundle, the docs recommend openclaw status --all as the safe shareable report: https://docs.openclaw.ai/help/faq