docs(cli): clarify delivery error fields · openclaw/openclaw@7903fe2
Kaspre
·
2026-05-10
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -91,7 +91,8 @@ Common fields:
|
91 | 91 | - `reason`: a lowercase snake-case reason from durable delivery or preflight validation. Known reasons include `cancelled_by_message_sending_hook`, `no_visible_payload`, `no_visible_result`, `channel_resolved_to_internal`, `unknown_channel`, `invalid_delivery_target`, and `no_delivery_target`; failed durable sends may also report the failed stage. Treat unknown values as opaque because the set can expand. |
92 | 92 | - `resultCount`: number of channel send results when available. |
93 | 93 | - `sentBeforeError`: `true` when a partial failure sent at least one payload before the error. |
94 | | -- `error` and `errorMessage`: present for failed or partial-failed sends. |
| 94 | +- `error`: boolean `true` for failed or partial-failed sends. |
| 95 | +- `errorMessage`: included only when an underlying delivery error message is captured. Preflight failures carry `error` and `reason` but no `errorMessage`. |
95 | 96 | - `payloadOutcomes`: optional per-payload results with `index`, `status`, `reason`, `resultCount`, `error`, `stage`, `sentBeforeError`, or hook metadata when available. |
96 | 97 | |
97 | 98 | ## Related |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
