openclaw - 💡(How to fix) Fix Cron scheduled task delivery fails (v2026.3.31) [1 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#59709Fetched 2026-04-08 02:41:30
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Participants

Fix Action

Workaround

  1. Use Heartbeat instead of Cron (executes in main session, delivery works)
  2. Manual push
RAW_BUFFERClick to expand / collapse

Bug Description

In OpenClaw v2026.3.31, Cron scheduled tasks execute successfully but QQ Bot delivery fails.

Reproduction Steps

  1. Create a Cron job with delivery configured to qqbot channel
  2. Run task: \openclaw cron run <job-id>\
  3. Task executes successfully, logs show \delivered: true\
  4. But no QQ push notification received

Expected Behavior

After Cron task execution succeeds, it should automatically push to the configured QQ session.

Actual Behavior

  • Logs show: \delivered: true, \deliveryStatus: delivered\
  • No push notification actually received
  • Manual \sessions_send\ works correctly

Environment

  • OpenClaw Version: 2026.3.31
  • OS: Windows 10.0.26200
  • Node.js: 24.14.0
  • Channel: QQ Bot (configured correctly, manual delivery works)

Possible Cause

Version 3.31 introduced unified Background Tasks system, delivery logic may have changed.

Workaround

  1. Use Heartbeat instead of Cron (executes in main session, delivery works)
  2. Manual push

Related Logs

\\json { "ts": 1775139092576, "jobId": "06fca6b0-6cf7-40d0-b778-ceb8c4abb860", "action": "finished", "status": "ok", "delivered": true, "deliveryStatus": "delivered" } \\


Please help investigate, thanks!

extent analysis

TL;DR

The issue with QQ Bot delivery failing after Cron task execution in OpenClaw v2026.3.31 may be resolved by using the Heartbeat instead of Cron or implementing a manual push as a temporary workaround.

Guidance

  • Investigate the unified Background Tasks system introduced in version 3.31 to understand changes in delivery logic that might be causing the issue.
  • Verify that the QQ Bot channel configuration is correct and functional by checking the successful manual delivery.
  • Review related logs for any patterns or clues that could indicate why delivered: true and deliveryStatus: delivered are logged but no push notification is received.
  • Consider testing the Heartbeat method as suggested in the workaround to see if it resolves the delivery issue.

Example

No specific code example is provided due to the lack of detailed implementation details in the issue description.

Notes

The provided information suggests a potential issue with the new Background Tasks system, but without more details on the implementation or logs showing the exact point of failure, it's challenging to provide a definitive fix. The suggested workarounds may help mitigate the issue temporarily.

Recommendation

Apply the workaround by using Heartbeat instead of Cron, as it is suggested that this method executes in the main session where delivery works, potentially bypassing the issue with the Background Tasks system.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING