vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 11:50:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(cron): clarify delivery modes

Browse Source
This commit is contained in:
Ayaan Zaidi
2026-04-21 09:40:36 +05:30
parent 4c1f187da0
commit 8d6ed34e4a
5 changed files with 27 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/help/faq.md
View File

@@ -1094,15 +1094,14 @@ for usage/billing and raise limits as needed.
<Accordion title="Cron fired, but nothing was sent to the channel. Why?">
Check the delivery mode first:
- `--no-deliver` / `delivery.mode: "none"` means no external message is expected.
- `--no-deliver` / `delivery.mode: "none"` means no runner fallback send is expected.
- Missing or invalid announce target (`channel` / `to`) means the runner skipped outbound delivery.
- Channel auth failures (`unauthorized`, `Forbidden`) mean the runner tried to deliver but credentials blocked it.
- A silent isolated result (`NO_REPLY` / `no_reply` only) is treated as intentionally non-deliverable, so the runner also suppresses queued fallback delivery.
For isolated cron jobs, the runner owns final delivery. The agent is expected
to return a plain-text summary for the runner to send. `--no-deliver` keeps
that result internal; it does not let the agent send directly with the
message tool instead.
For isolated cron jobs, the agent can still send directly with the `message`
tool when a chat route is available. `--announce` only controls the runner
fallback path for final text that the agent did not already send.
Debug: