Why does active-memory make Telegram unresponsive?

The active-memory plugin's embedded sub-agent run blocks the Node.js event loop, preventing Telegram long-polling from processing updates. The agent goes permanently unresponsive.

How to diagnose active-memory event loop blocking?

Disable the active-memory plugin. If Telegram responsiveness immediately returns, the active-memory sub-agent is the cause. Reproducible 100% across restart cycles.

Which OpenClaw versions have the active-memory blocking bug?

Reported on versions 2026.4.12 through 2026.4.15. Related timeout issues also reported on v2026.4.14.

Can I use active-memory without blocking Telegram?

Currently no reliable workaround. The sub-agent call needs to be made async or run in a worker thread to avoid blocking the event loop.

Is this related to the active-memory timeout issues?

Yes, GitHub issues #65517, #68825, #66849, and #66708 all describe different aspects of active-memory causing performance degradation.

← Back to dashboard

clawsmith.com/signal/openclaw-active-memory-blocks-event-loop-telegram-permanent-stall

⚠ IssueWide OpencoreLive

Active-Memory Plugin Blocks Node.js Event Loop, Permanently Starving Telegram Polling

Enabling active-memory plugin causes embedded sub-agent run to block the Node.js event loop, permanently starving Telegram long-polling. Agent goes unresponsive. Disabling active-memory immediately restores responsiveness. Reproducible 100% across 5+ restart cycles.