foggy vine
Hey @hollow rock — hitting a consistent Telegram initialization freeze on Windows that's making the gateway unusable.
Setup: OpenClaw 2026.4.27, Windows 11, Node 22.14, 2 plugins (router-plugin, telegram). memory-core disabled, pricing.enabled: false, memorySearch.enabled: false.
Symptom: ~34s event loop freeze on every boot, right after the WS approval handshake. Telegram attempts getUpdates during the freeze, times out, never completes — (@Carson797_bot) never appears. Gateway runs but Carson has no channel.
Relevant log lines:
[telegram] [default] starting provider ← no (@botname)
[ws] ⇄ res ✓ exec.approval.list 373ms
[telegram] fetch fallback: DNS-resolved IP unreachable; trying alternative Telegram API IP
[diagnostic] liveness warning: eventLoopDelayP99Ms=34309 eventLoopDelayMaxMs=34309 eventLoopUtilization=1
Ruled out: Jiti compilation (plugin pre-compiled to JS, loads before the freeze), memory-core, pricing fetches, memorySearch, bad token. Freeze is consistently 34s, P99=Max — one sustained synchronous block.
Had one clean boot where (@Carson797_bot) appeared and everything worked — identical config, never reproduced.
Is this a known Windows issue in 4.27? Any config option to delay Telegram startup or is it fixed in a newer build?