Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Matrix channel syncs (HTTP 200) but receives no messages - similar to #54069 [12 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#61773•Fetched 2026-04-08 02:54:41
View on GitHub
Comments
12
Participants
3
Timeline
20
Reactions
0
Author
davidvvdavidvv
Participants
davidvvdavidvvgumadeirasgumadeirasjtorontojtoronto
Timeline (top)
commented ×12mentioned ×4subscribed ×4

Matrix channel shows as connected and syncs successfully (HTTP 200 responses from homeserver), but no incoming messages are ever received or processed by the bot. Telegram channel works normally.

This appears to be the same underlying issue as #54069, but occurring without the hot-reload trigger described there.

Error Message

Matrix sync shows successful connections:

  • Matrix channel starts and connects
  • Sync requests return HTTP 200
  • No event dispatch errors (because no events are dispatched at all)
  • Complete silence after initial startup

Root Cause

Matrix sync shows successful connections:

  • Matrix channel starts and connects
  • Sync requests return HTTP 200
  • No event dispatch errors (because no events are dispatched at all)
  • Complete silence after initial startup

Fix Action

Workaround

None found. Matrix channel is non-functional until this is resolved.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (Matrix channel connected but non-functional)

Summary

Matrix channel shows as connected and syncs successfully (HTTP 200 responses from homeserver), but no incoming messages are ever received or processed by the bot. Telegram channel works normally.

This appears to be the same underlying issue as #54069, but occurring without the hot-reload trigger described there.

Steps to Reproduce

  1. Configure Matrix channel with valid credentials (access token, homeserver URL)
  2. Start OpenClaw gateway
  3. Matrix channel shows as connected in status
  4. Send messages to bot account in Matrix (DM or room)
  5. Bot never receives or responds to messages

Expected Behavior

Matrix channel receives incoming messages and dispatches them to the agent for processing.

Actual Behavior

  • Matrix channel connects successfully
  • Sync loop runs with HTTP 200 responses (some returning in ~25ms indicating new events exist)
  • No messages are ever dispatched to the agent
  • No errors or warnings in logs — complete silence after startup
  • Bot is visible online in Matrix clients
  • Telegram channel works normally

Investigation Performed

  • Verified Matrix account works by logging in separately via Element — messages send/receive correctly
  • Confirmed DM room is properly joined on both sides
  • Tested sending messages from bot account in Element — works fine
  • Sync logs show successful HTTP 200 responses from /sync endpoint
  • No error messages in OpenClaw logs
  • Token is valid and not expired
  • Homeserver URL is correct

OpenClaw version

2026.3.23 (latest as of 2026-04-06)

Operating system

Linux 6.17.0-20-generic (x64), Ubuntu

Install method

npm (global install)

Logs

Matrix sync shows successful connections:

  • Matrix channel starts and connects
  • Sync requests return HTTP 200
  • No event dispatch errors (because no events are dispatched at all)
  • Complete silence after initial startup

Impact and severity

Severity: High — Matrix channel completely non-functional

Affected: All Matrix deployments using current version

Frequency: Permanent, not intermittent

Consequence: Matrix bot unusable, all messages missed

Additional context

This issue matches the symptoms described in #54069 (Matrix channel stops dispatching events), but occurs without the config hot-reload trigger mentioned there. The original issue was closed, but the underlying bug appears to still be present.

Key observation: The MatrixClient sync layer functions correctly (HTTP 200 responses, sync loop runs), but OpenClaw's event dispatcher never fires. This suggests the bug is in the event dispatch/handling layer, not the sync layer.

Workaround

None found. Matrix channel is non-functional until this is resolved.

extent analysis

TL;DR

The issue can be addressed by investigating and fixing the event dispatch/handling layer in OpenClaw, as the sync layer appears to be functioning correctly.

Guidance

  • Review the event dispatch code in OpenClaw to identify why events are not being fired, despite successful sync responses.
  • Verify that the event handling logic is correctly configured and enabled for the Matrix channel.
  • Check for any differences in event handling between the Matrix and Telegram channels, as the latter is working normally.
  • Investigate the relationship between the current issue and the previously reported #54069, to determine if the same underlying bug is causing the problem.

Example

No specific code snippet can be provided without more information on the OpenClaw event dispatch code, but a general example of event handling might look like:

def handle_matrix_event(event):
    # Process the event and dispatch to the agent
    pass

def matrix_sync_loop():
    # Sync with the Matrix homeserver and retrieve events
    events = sync_with_homeserver()
    for event in events:
        handle_matrix_event(event)

Notes

The issue appears to be specific to the Matrix channel and is not intermittent, suggesting a consistent problem with the event dispatch logic. The fact that the Telegram channel is working normally implies that the issue is not with the overall event handling architecture, but rather with the specific implementation for Matrix.

Recommendation

Apply a workaround or fix to the event dispatch/handling layer, as the root cause of the issue appears to be related to this component. Until a fix is available, the Matrix channel will remain non-functional.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#model compatibility#GPU setup#container setup#orchestration issue#cache issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING