Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Cron ???????? (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#59707•Fetched 2026-04-08 02:41:33
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
bxy3045134656bxy3045134656
Participants
bxy3045134656bxy3045134656
Timeline (top)
closed ×1locked ×1
RAW_BUFFERClick to expand / collapse

Bug ??

OpenClaw v2026.3.31 ???,Cron ????????? QQ Bot ?????

????

  1. ?? Cron ??,?? delivery ? qqbot ??
  2. ????:openclaw cron run <job-id>
  3. ??????,???? delivered: true
  4. ?????? QQ ??

????

Cron ???????,?????????? QQ ???

????

  • ????:delivered: true, deliveryStatus: delivered
  • ???????
  • ???? sessions_send ??????

????

  • OpenClaw ??:2026.3.31
  • ????:Windows 10.0.26200
  • Node.js ??:24.14.0
  • Channel: QQ Bot (????,??????)

????

3.31 ????????????????(Background Tasks),???????????

??????

  1. ?? Heartbeat ?? Cron(??????,????)
  2. ????

????

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

?????????,??!

extent analysis

TL;DR

Investigate the discrepancy between the delivered: true status and the actual delivery failure of QQ Bot messages in OpenClaw v2026.3.31.

Guidance

  • Review the Cron job logs to verify if the job is successfully running and completing without errors.
  • Check the sessions_send logs to see if there are any issues with the message delivery process.
  • Investigate potential issues with the QQ Bot channel configuration or integration with OpenClaw.
  • Verify that the deliveryStatus field in the JSON response accurately reflects the delivery status of the messages.

Example

No code snippet is provided as the issue does not contain sufficient information to create a relevant example.

Notes

The issue seems to be related to a specific version of OpenClaw (v2026.3.31) and a particular channel (QQ Bot), which may indicate a version-specific or channel-specific bug. Further investigation is needed to determine the root cause of the issue.

Recommendation

Apply workaround: Investigate and resolve the discrepancy between the delivered: true status and the actual delivery failure, as upgrading to a fixed version is not explicitly implied in the issue.

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…
#GPU setup#container setup#orchestration issue#cache issue#memory leak

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 Cron ???????? (v2026.3.31) [1 participants]