Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: 4.21 is making cron jobs send unnecessary confirmation messages [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#70433•Fetched 2026-04-23 07:24:52
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
theDanielJLewistheDanielJLewis
Participants
theDanielJLewistheDanielJLewis
Timeline (top)
labeled ×2

After upgrading from 2026.4.14 to 2026.4.21, my hourly cron job has started posting "confirmation" type messages to my Slack channel after it already posted the message the job tells it to post.

These messages are like, "[job] delivered to Slack channel #[channel name]," or even posting the JSON code the cron job generates.

I have told it multiple times to stop sending those messages, telling it to update the job, but I gave up and moved back to 4.14.

Root Cause

After upgrading from 2026.4.14 to 2026.4.21, my hourly cron job has started posting "confirmation" type messages to my Slack channel after it already posted the message the job tells it to post.

These messages are like, "[job] delivered to Slack channel #[channel name]," or even posting the JSON code the cron job generates.

I have told it multiple times to stop sending those messages, telling it to update the job, but I gave up and moved back to 4.14.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

After upgrading from 2026.4.14 to 2026.4.21, my hourly cron job has started posting "confirmation" type messages to my Slack channel after it already posted the message the job tells it to post.

These messages are like, "[job] delivered to Slack channel #[channel name]," or even posting the JSON code the cron job generates.

I have told it multiple times to stop sending those messages, telling it to update the job, but I gave up and moved back to 4.14.

Steps to reproduce

Sorry, I can't share my specific job, but I'm hoping others have seen similar behavior regressions.

Expected behavior

I expected my cron job(s) to post only the mesages I told them to post, and no unnecessary followups, confirmations, or results.

Actual behavior

The cron job posts messages like, "[job] delivered to Slack channel #[channel name]," or even posting the JSON code the cron job generates. I can't get it to stop.

OpenClaw version

2026.4.21

Operating system

macOS Tahoe

Install method

npm global

Model

GPT-5.4

Provider / routing chain

I don't know.

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

Downgrade to version 2026.4.14 as a temporary workaround to prevent the cron job from posting unnecessary confirmation messages.

Guidance

  • Verify that the issue is specific to version 2026.4.21 by testing the cron job with different versions.
  • Check the cron job configuration for any changes that may be causing the unnecessary messages.
  • Investigate if there are any updates or patches available for version 2026.4.21 that may resolve the issue.
  • Consider reaching out to the OpenClaw community or support team for further assistance, as the issue may be related to a regression in the new version.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The root cause of the issue is unclear, and without more information, it's difficult to provide a definitive solution. The suggested workaround is based on the fact that the issue started after upgrading to version 2026.4.21.

Recommendation

Apply workaround: Downgrade to version 2026.4.14, as it is known to work correctly and prevents the unnecessary confirmation messages from being posted.

FAIL-SAFE

If the issue persists or more information is needed, consider seeking additional support from the OpenClaw community or support team.

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…

FAQ

Expected behavior

I expected my cron job(s) to post only the mesages I told them to post, and no unnecessary followups, confirmations, or results.

#embedding generation#cache error#pipeline error#runtime error#dependency conflict

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]: 4.21 is making cron jobs send unnecessary confirmation messages [1 participants]