Cron 兼容修复：显式 delivery 与 legacy payload.deliver 分流

场景：isolated cron 作业修复重复投递后，旧版 payload.deliver 作业可能行为变化。该补丁通过 delivery plan 来源判定，兼顾新配置正确性与旧作业兼容性。

GITHUBDiscovered 2026-02-14Author brandonwise

Prerequisites

Your deployment uses isolated cron jobs and may still contain legacy payload.deliver fields.
You can inspect cron job definitions and run history before/after upgrade.

Steps

Inventory existing cron jobs and classify them into explicit delivery vs legacy payload.deliver styles.
Upgrade to a build containing PR #15737, then restart gateway in maintenance window.
Run one representative job from each class (manual + scheduled) and capture output channels.
Confirm explicit delivery jobs are handled by isolated announce flow, while legacy jobs keep expected relay behavior.

Commands

openclaw cron list

openclaw cron run <jobId>

openclaw cron runs <jobId>

openclaw gateway restart

Verify

After upgrade, explicit-delivery jobs send exactly once, and legacy payload-only jobs still deliver according to prior expectations.

Caveats

Mixed config in a single job can make delivery source ambiguous; migrate to explicit delivery for clarity.
Channel-provider retries can still produce perceived duplicates unrelated to scheduler core（需验证）.

Source attribution

This tip is aggregated from community/public sources and preserved with attribution.