Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Cron jobs with tools enabled cause delivery failure and silent fallback to DM

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…

Cron jobs configured with delivery: announce to a WhatsApp group fail to deliver when the model has access to tools. The model attempts to send the message itself via a message tool (which fails), and the system silently falls back to delivering to the owner's DM instead of the intended group.

Root Cause

Cron jobs configured with delivery: announce to a WhatsApp group fail to deliver when the model has access to tools. The model attempts to send the message itself via a message tool (which fails), and the system silently falls back to delivering to the owner's DM instead of the intended group.

Fix Action

Workaround

Create cron jobs with --tools "" to prevent the model from accessing tools.

RAW_BUFFERClick to expand / collapse

Summary

Cron jobs configured with delivery: announce to a WhatsApp group fail to deliver when the model has access to tools. The model attempts to send the message itself via a message tool (which fails), and the system silently falls back to delivering to the owner's DM instead of the intended group.

Steps to Reproduce

  1. Create a cron job with --announce --to <group-id> --channel whatsapp
  2. Leave tools enabled (default)
  3. Wait for the cron to fire

Expected Behavior

Model generates text, announce delivery sends it to the configured group.

Actual Behavior

  1. Model receives tools in context and attempts to use a message-sending tool
  2. Tool call fails
  3. Diagnostic shows: "Message failed"
  4. System falls back to DM delivery to the owner
  5. cron show still reports status: ok and delivered: true
  6. The delivery.resolved shows the DM, not the group

Workaround

Create cron jobs with --tools "" to prevent the model from accessing tools.

Impact

Messages intended for groups silently go to the wrong destination. The job reports success, making it hard to diagnose.

Environment

  • OpenClaw: 2026.5.12, 2026.5.18
  • Tested with: google/gemini-2.5-flash, google/gemini-3-flash-preview

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…
#index setup#retrieval issue#search optimization#API routing#API middleware

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 jobs with tools enabled cause delivery failure and silent fallback to DM