memory-lancedb-pro causes Telegram providers to stop starting

[yyxp1989]

Plugin Version

1.1.0-beta.10

OpenClaw Version

2026.3.23-2 (7ffe7e4)

Bug Description

Bug report

OpenClaw version

2026.3.23-2

Previous version / migration source

Config migrated from 2026.2.18

Environment

• Debian/Linux
• Node v22.22.1

What happened

After enabling memory-lancedb-pro, all Telegram bots stopped responding.

At the same time:

• OpenClaw gateway remained functional
• TUI remained functional
• memory-lancedb-pro initialized successfully

Disabling memory-lancedb-pro restored Telegram immediately.

────────────────────────────────────────────────────────────────────────────────

Actual behavior

When memory-lancedb-pro is enabled:

• Telegram bots do not respond
• no Telegram provider startup logs appear
• gateway/TUI still work

When the plugin is disabled:

• Telegram works normally again

────────────────────────────────────────────────────────────────────────────────

Expected Behavior

Expected behavior

Telegram providers should still start and respond normally when memory-lancedb-pro is
enabled.

Steps to Reproduce

What I already tested

1. Config schema migration

Checked current docs for 2026.3.23-2:

• channels.telegram still valid
• bindings still valid
• plugins.entries still valid

So this does not appear to be caused by obsolete config categories from 2026.2.18.

2. Telegram multi-account config

Reduced Telegram to a minimal single-account config using only:

• channels.telegram.enabled
• channels.telegram.botToken
• dmPolicy
• allowFrom
• groupPolicy
• groups
• streaming

Result: same issue.

3. Plugin load order

Tried different plugin orders:

• Telegram before memory plugin
• memory plugin first
• other permutations

Result: no change.

4. Gateway service entrypoint

Fixed a stale openclaw-gateway.service ExecStart pointing to an old entrypoint and updated
it to the current installed dist/index.js.

Result: gateway service issue fixed, but Telegram still did not start when
memory-lancedb-pro was enabled.

5. Manual regression check

I manually verified that:

• without memory-lancedb-pro, Telegram works
• with memory-lancedb-pro, Telegram stops responding

────────────────────────────────────────────────────────────────────────────────

Reproduction steps

1. Start from a working OpenClaw install with Telegram configured
2. Confirm Telegram bots respond normally
3. Enable memory-lancedb-pro
4. Restart gateway
5. Telegram stops responding
6. Disable memory-lancedb-pro
7. Restart gateway
8. Telegram works again

────────────────────────────────────────────────────────────────────────────────

Additional note

Telegram runtime files and plugin manifests are present in the installed OpenClaw package,
so this does not appear to be a missing Telegram package.

This looks more like a plugin lifecycle / channel initialization compatibility issue.

Error Logs / Screenshots

### Relevant logs                                                                          
                                                                                            
 memory-lancedb-pro always initializes successfully:                                        
                                                                                            
                                                                                     
   memory-lancedb-pro@1.1.0-beta.10: plugin registered                                       
   memory-lancedb-pro: initialized successfully (embedding: OK, retrieval: OK, mode:        
 hybrid, FTS: enabled)                                                                      
                                                                                         
                                                                                            
 Gateway also detects Telegram config changes, but after restart there are still no logs    
 like:                                                                                      
                                                                                            
                                                                                     
   [gateway/channels/telegram] [default] starting provider ...                              
                                                                                         
                                                                                            
 So Telegram config is being recognized, but provider startup does not happen.

Embedding Provider

None

OS / Platform

debian13

[iversonpuppets]

I am facing the same issue.