You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/automation/cron-jobs.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -199,6 +199,7 @@ Failure notifications follow a separate destination path:
199
199
- If neither is set and the job already delivers via `announce`, failure notifications now fall back to that primary announce target.
200
200
-`delivery.failureDestination` is only supported on `sessionTarget="isolated"` jobs unless the primary delivery mode is `webhook`.
201
201
-`failureAlert.includeSkipped: true` opts a job or global cron alert policy into repeated skipped-run alerts. Skipped runs keep a separate consecutive skip counter, so they do not affect execution-error backoff.
202
+
-`failureAlert.threadId` routes threshold alerts to a channel thread or topic. When the alert uses the job's primary announce target and does not set its own `to`, it inherits `delivery.threadId`; if it names a separate destination, set `failureAlert.threadId` explicitly.
Copy file name to clipboardExpand all lines: docs/cli/cron.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,6 +84,8 @@ Failure notifications resolve in this order:
84
84
2. Global `cron.failureDestination`.
85
85
3. The job's primary announce target (when no explicit failure destination is set).
86
86
87
+
Per-job `failureAlert.threadId` routes threshold alerts to a channel thread or topic, such as a Telegram forum topic. When a failure alert uses the job's primary announce target and does not set its own `to`, OpenClaw reuses `delivery.threadId` so failures land beside the corresponding success announcement. If `failureAlert.to` names a separate destination, set `failureAlert.threadId` explicitly when that destination needs a topic.
88
+
87
89
<Note>
88
90
Main-session jobs may only use `delivery.failureDestination` when primary delivery mode is `webhook`. Isolated jobs accept it in all modes.
89
91
</Note>
@@ -239,6 +241,16 @@ Announce to a Telegram forum topic:
Copy file name to clipboardExpand all lines: docs/gateway/configuration-reference.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1333,6 +1333,7 @@ One-shot jobs stay enabled until retry attempts are exhausted, then disable whil
1333
1333
cooldownMs:3600000,
1334
1334
includeSkipped:false,
1335
1335
mode:"announce",
1336
+
threadId:79,
1336
1337
accountId:"main",
1337
1338
},
1338
1339
},
@@ -1344,6 +1345,7 @@ One-shot jobs stay enabled until retry attempts are exhausted, then disable whil
1344
1345
-`cooldownMs`: minimum milliseconds between repeated alerts for the same job (non-negative integer).
1345
1346
-`includeSkipped`: count consecutive skipped runs toward the alert threshold (default: `false`). Skipped runs are tracked separately and do not affect execution-error backoff.
1346
1347
-`mode`: delivery mode - `"announce"` sends via a channel message; `"webhook"` posts to the configured webhook.
1348
+
-`threadId`: optional channel thread or topic id for threshold alerts. If omitted and the alert uses a job's primary announce target, OpenClaw inherits the job's `delivery.threadId`.
1347
1349
-`accountId`: optional account or channel id to scope alert delivery.
0 commit comments