openclaw - 💡(How to fix) Fix [Bug]: Isolated cron task summaries routed to Telegram despite notify: silent [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#71726Fetched 2026-04-26 05:09:18
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×2

My agent (Scorchio, running OpenClaw) generated this issue — Garry12gg is posting it on its behalf.

Bug description: Isolated cron job sessions are sending their terminalSummary to Telegram even when notifyPolicy is set to silent and deliveryStatus is not_applicable. The task summaries land in the Telegram chat alongside the actual content, resulting in duplicate messages.

Root Cause

My agent (Scorchio, running OpenClaw) generated this issue — Garry12gg is posting it on its behalf.

Bug description: Isolated cron job sessions are sending their terminalSummary to Telegram even when notifyPolicy is set to silent and deliveryStatus is not_applicable. The task summaries land in the Telegram chat alongside the actual content, resulting in duplicate messages.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

My agent (Scorchio, running OpenClaw) generated this issue — Garry12gg is posting it on its behalf.

Bug description: Isolated cron job sessions are sending their terminalSummary to Telegram even when notifyPolicy is set to silent and deliveryStatus is not_applicable. The task summaries land in the Telegram chat alongside the actual content, resulting in duplicate messages.

Steps to reproduce

  1. Set up an isolated cron job with sessionTarget: "isolated" and default notify policy (silent)
  2. The cron fires, generates content, sends it to Telegram via message tool
  3. A second system message appears in Telegram containing the task's terminalSummary ("Sent! Here's a summary of what was delivered...")

Expected behavior

With notifyPolicy: silent, no task summary should be delivered to the user. Only the content generated by the cron should appear.

Actual behavior

Both the cron content AND the task terminal summary appear in Telegram.

Task ID example

d35a3758-4460-4d81-b33a-75c09b7b5abd (Off-Day Morning Weather, Apr 25)

OpenClaw version

2026.4.23

Operating system

OS: Linux (Docker container on cloud) — kernel 5.10.134-19.2.al8.x86_64, Node.js v22.22.2

Install method

No response

Model

MiniMax (via OpenClaw with MiniMax plugin)

Provider / routing chain

OpenClaw Gateway (ws://127.0.0.1:18789) → MiniMax plugin → MiniMax API

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

Note added by Garry12gg: This is not my local instance. It it running on www.talkie-ai.com via the "Talkie Claw" option.

extent analysis

TL;DR

The issue can be resolved by modifying the notify policy to exclude terminal summaries for isolated cron jobs.

Guidance

  • Review the OpenClaw configuration to ensure that the notify policy is correctly set to silent for isolated cron jobs.
  • Check the message tool settings to see if there's an option to disable sending terminal summaries for silent notify policies.
  • Investigate the MiniMax plugin configuration to determine if it's overriding the notify policy or sending the terminal summary separately.
  • Verify that the issue is not specific to the "Talkie Claw" option on www.talkie-ai.com by testing with a different setup.

Example

No code snippet is provided as the issue seems to be related to configuration rather than code.

Notes

The issue might be specific to the OpenClaw version (2026.4.23) or the MiniMax plugin, so testing with different versions or plugins could help isolate the cause.

Recommendation

Apply a workaround by modifying the notify policy or message tool settings to exclude terminal summaries for isolated cron jobs, as the root cause is likely related to the configuration rather than a bug in the code.

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

With notifyPolicy: silent, no task summary should be delivered to the user. Only the content generated by the cron should appear.

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]: Isolated cron task summaries routed to Telegram despite notify: silent [1 participants]