Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: openclaw system event silently swallowed since 2026.3.12 — gateway never logs receipt or sends message [1 comments, 2 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#53691•Fetched 2026-04-08 01:24:44
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Author
mikeevenssplashmikeevenssplash
Participants
mikeevenssplashmikeevenssplasholdjsoldjs
Timeline (top)
commented ×1

openclaw system event --text "..." --mode now returns {"ok": true} but the gateway never logs receipt of the event and no message is delivered. Regression introduced in 2026.3.12 (released 12 March 2026).

Root Cause

openclaw system event --text "..." --mode now returns {"ok": true} but the gateway never logs receipt of the event and no message is delivered. Regression introduced in 2026.3.12 (released 12 March 2026).

Code Example

openclaw system event --text "Test ping" --mode now --json
# Returns: {"ok": true}

---

2026-03-04T19:38:56.939Z [ws] ⇄ res ✓ system-event 98ms
2026-03-05T13:21:36.827Z [ws] ⇄ res ✓ system-event 299ms
RAW_BUFFERClick to expand / collapse

Summary

openclaw system event --text "..." --mode now returns {"ok": true} but the gateway never logs receipt of the event and no message is delivered. Regression introduced in 2026.3.12 (released 12 March 2026).

Steps to Reproduce

openclaw system event --text "Test ping" --mode now --json
# Returns: {"ok": true}

Then check gateway log — no system-event entry appears.

Expected Behaviour

Gateway logs [ws] ⇄ res ✓ system-event and triggers a session turn that delivers a message to the configured channel (Telegram in this case).

Actual Behaviour

CLI returns ok: true but gateway log shows no system-event entry. No message is sent. The event is silently swallowed.

Evidence from Gateway Log

Last working system-event entries (pre-2026.3.12):

2026-03-04T19:38:56.939Z [ws] ⇄ res ✓ system-event 98ms
2026-03-05T13:21:36.827Z [ws] ⇄ res ✓ system-event 299ms

Update to 2026.3.12 applied: 2026-03-13T07:56:21

Zero system-event log entries since update (19 days). CLI continues to return ok: true on every call.

Impact

  • Subagent completion pings silently dropped
  • Cron job announce events not delivered
  • Manual wake events (--mode now) non-functional
  • Any workflow relying on openclaw system event for notification has been broken since 13 March

Environment

  • OpenClaw version: 2026.3.23-2 (current, issue present across all versions since 2026.3.12)
  • Platform: macOS (Darwin arm64)
  • Channel: Telegram
  • Auth mode: token

extent analysis

Fix Plan

The fix involves updating the openclaw system event handling to properly log and deliver events.

  • Step 1: Check the openclaw configuration file for any changes or updates related to system event handling.
  • Step 2: Update the system-event handler to include logging and delivery of events.

Example code snippet (in Python):

import logging

# ...

def handle_system_event(event):
    # Log the event
    logging.info(f"[ws] ⇄ res ✓ system-event {event['text']}")

    # Deliver the event to the configured channel (Telegram)
    telegram_channel = get_telegram_channel()
    telegram_channel.send_message(event['text'])

    return {"ok": True}
  • Step 3: Verify that the handle_system_event function is being called correctly when a system event is triggered.

Verification

To verify that the fix worked:

  • Run the openclaw system event command with the --json flag.
  • Check the gateway log for the system-event entry.
  • Verify that the message is delivered to the configured channel (Telegram).

Example verification command:

openclaw system event --text "Test ping" --mode now --json

Check the gateway log for the system-event entry:

[ws] ⇄ res ✓ system-event Test ping

Verify that the message is delivered to the Telegram channel.

Extra Tips

  • Make sure to update the openclaw version to the latest release.
  • Check the openclaw documentation for any changes or updates related to system event handling.
  • Test the openclaw system event command with different event types and modes to ensure that it is working correctly.

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…
#prompt issue#agent setup#task chaining#parallel task#integration 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