Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] cron run + systemEvent + sessionTarget=main still results in deliveryStatus: "not-requested" on v2026.4.26 (regression from #60262 / #62296) [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#73777•Fetched 2026-04-29 06:15:21
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
vokasugvokasug
Participants
clawsweeper[bot]clawsweeper[bot]vokasugvokasug
Timeline (top)
commented ×1cross-referenced ×1

Code Example

{
  "name": "Test systemEvent",
  "sessionTarget": "main",
  "payload": {
    "kind": "systemEvent",
    "text": "Please check something and report back"
  }
}

---

{
  "action": "finished",
  "status": "ok",
  "durationMs": 12,
  "deliveryStatus": "not-requested"
}
RAW_BUFFERClick to expand / collapse

Bug Description

On OpenClaw v2026.4.26, cron jobs with payload.kind: "systemEvent" and sessionTarget: "main" still silently fail when manually triggered via cron run (both CLI and Control UI "Run" button). The run completes in ~12-31ms with deliveryStatus: "not-requested" and no actual execution.

This appears to be a regression or incomplete fix for previously closed issues #60262 and #62296.

Steps to Reproduce

  1. Create a cron job with systemEvent payload targeting main session:
{
  "name": "Test systemEvent",
  "sessionTarget": "main",
  "payload": {
    "kind": "systemEvent",
    "text": "Please check something and report back"
  }
}

  1. Trigger it via CLI: openclaw cron run --id <job-id> or click "Run" in Control UI

  2. Check run result: openclaw cron runs --id <job-id>

Expected Behavior

The system event should be delivered to the main session, causing the agent to wake up and execute the task.

Actual Behavior

{
  "action": "finished",
  "status": "ok",
  "durationMs": 12,
  "deliveryStatus": "not-requested"
}

No agent turn is created. The task is not executed.

Environment

  • OpenClaw: v2026.4.26
  • Node: v22.22.2
  • OS: Linux 6.6.87.2-microsoft-standard-WSL2

Related Issues

  • #60262 — [Bug]: Cron jobs fire but don't wake agent sessions (mentioned fix commit 435018a)
  • #62296 — memory-core dreaming cron system-event does not trigger before_agent_reply hook
  • #7065 — Cron job system events are ignored during heartbeat execution
  • #19438 — wake() in cron/service/timer.ts calls enqueueSystemEvent (fixed in 98feb9f)

Additional Context

The same job works correctly when triggered naturally via scheduled heartbeat poll. The issue is specifically with manual cron run trigger (both CLI cron run and Control UI "Run" button).

extent analysis

TL;DR

Manually triggered cron jobs with payload.kind: "systemEvent" and sessionTarget: "main" may require adjustments to handle the deliveryStatus: "not-requested" issue, potentially involving changes to the cron job configuration or the underlying system event handling.

Guidance

  • Review the commit history and changes made in fixes for related issues #60262 and #62296 to understand potential regressions or incomplete fixes.
  • Verify that the cron run command and Control UI "Run" button are correctly configured to handle system events, considering the differences between manual and scheduled triggers.
  • Investigate the system event handling logic to ensure it correctly processes events triggered manually via cron run, potentially involving adjustments to the enqueueSystemEvent function or related components.
  • Check for any environment-specific issues, such as Node or OS version incompatibilities, that might be contributing to the problem.

Example

No specific code snippet can be provided without further information on the underlying system event handling logic. However, reviewing the cron/service/timer.ts file and the enqueueSystemEvent function, as mentioned in issue #19438, may provide insight into the issue.

Notes

The issue seems to be specific to manual triggers via cron run and may not be directly related to the cron job configuration itself. The fact that the job works correctly when triggered naturally via scheduled heartbeat poll suggests a potential issue with the manual trigger handling.

Recommendation

Apply workaround: Given the potential complexity of the issue and the involvement of multiple related problems, applying a workaround, such as modifying the cron job to use a different trigger method or adjusting the system event handling logic, may be the most practical solution until a more permanent fix can be implemented.

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 save/load#optimization#mixed precision#training loop#device allocation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug] cron run + systemEvent + sessionTarget=main still results in deliveryStatus: "not-requested" on v2026.4.26 (regression from #60262 / #62296) [1 comments, 2 participants]