Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Cron job incorrectly reports 'Message failed' despite successful delivery [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#73556•Fetched 2026-04-29 06:18:15
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Barclay1895Barclay1895
Participants
Barclay1895Barclay1895

Error Message

Cron jobs with explicit delivery.mode="announce" and explicit channel/to targets are delivering messages successfully (confirmed by delivered: true and deliveryStatus: "delivered" in run logs), but the job status is being marked as "error" with the error message "⚠️ ✉️ Message failed". Job status is "error" despite successful delivery. "status": "error", "error": "⚠️ ✉️ Message failed",

Fix Action

Fix / Workaround

Notes:

  • cron.failureAlert config paths appear to be protected, preventing user mitigation
  • This appears to be a race condition in delivery status confirmation logic

Code Example

{
  "status": "error",
  "error": "⚠️ ✉️ Message failed",
  "delivered": true,
  "deliveryStatus": "delivered",
  "delivery": {
    "resolved": { "ok": true, "channel": "telegram", "to": "8703673087" },
    "delivered": true
  }
}
RAW_BUFFERClick to expand / collapse

Description: Cron jobs with explicit delivery.mode="announce" and explicit channel/to targets are delivering messages successfully (confirmed by delivered: true and deliveryStatus: "delivered" in run logs), but the job status is being marked as "error" with the error message "⚠️ ✉️ Message failed".

This triggers false failure notifications to users.

Reproduction:

  • Job: solis-battery-report running every 30 minutes
  • Delivery config: explicit channel: telegram, to: 8703673087
  • ~15% of runs show this pattern

Expected behavior: If delivered: true and deliveryStatus: "delivered", job status should be "ok".

Actual behavior: Job status is "error" despite successful delivery.

Sample run log (excerpt):

{
  "status": "error",
  "error": "⚠️ ✉️ Message failed",
  "delivered": true,
  "deliveryStatus": "delivered",
  "delivery": {
    "resolved": { "ok": true, "channel": "telegram", "to": "8703673087" },
    "delivered": true
  }
}

Environment:

  • OpenClaw version: 2026.4.2
  • Host: Linux x64
  • Channel: Telegram

Notes:

  • cron.failureAlert config paths appear to be protected, preventing user mitigation
  • This appears to be a race condition in delivery status confirmation logic

extent analysis

TL;DR

The job status is being marked as "error" despite successful message delivery, likely due to a race condition in delivery status confirmation logic, and a potential workaround is to review and adjust the delivery status confirmation logic.

Guidance

  • Review the OpenClaw version 2026.4.2 documentation to see if there are any known issues or patches related to delivery status confirmation logic.
  • Investigate the cron.failureAlert config paths to determine if there are any potential workarounds or modifications that can be made to prevent false failure notifications.
  • Analyze the run logs to identify any patterns or correlations between the successful deliveries and the error messages.
  • Consider reaching out to the OpenClaw support team or community forums to report the issue and gather more information about potential fixes or workarounds.

Example

No code snippet is provided as the issue appears to be related to the OpenClaw configuration and logic rather than a specific code implementation.

Notes

The issue appears to be specific to the OpenClaw version 2026.4.2 and the Telegram channel, and may not be reproducible in other environments or versions. Additionally, the cron.failureAlert config paths being protected may limit the ability to implement a user-level mitigation.

Recommendation

Apply workaround: Given the potential race condition in delivery status confirmation logic, it may be necessary to implement a custom workaround, such as modifying the job status checking logic or implementing a delay between delivery and status checking, to prevent false failure notifications.

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…
#docker error#permission error#memory optimization#batch processing#GPU compatibility

Still need to ship something?

×6

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

Back to top recommendations

TRENDING