openclaw - 💡(How to fix) Fix Cron job delivery missing `to` field for openclaw-weixin

Bug Description

When creating one-off cron jobs (scheduled tasks) targeting the openclaw-weixin channel, the delivery.to field is occasionally not populated, causing the job to fail with a "requires target" error at execution time.

Affected Version

OpenClaw v2026.4.26 (17c3fa238f70)

Reproduction Steps

1. Create a one-off cron job with delivery.channel: "openclaw-weixin" and delivery.mode: "announce"
2. Leave delivery.to unspecified during creation
3. When the job triggers, it fails with error: "Delivering to openclaw-weixin requires target"

Expected Behavior

When delivery.channel is set to openclaw-weixin and the session context has a known chat ID (e.g. [email protected]), the delivery.to field should be automatically populated with the session's chat ID.

Actual Behavior

The delivery.to field is sometimes missing from the saved job configuration.

Broken job (missing to):

{
  "delivery": {
    "mode": "announce",
    "channel": "openclaw-weixin",
    "accountId": "5777c963aa4d-im-bot"
  }
}

Working job (has to):

{
  "delivery": {
    "mode": "announce",
    "channel": "openclaw-weixin",
    "to": "[email protected]",
    "accountId": "5777c963aa4d-im-bot"
  }
}

Impact

In my instance, 5 out of ~20 openclaw-weixin cron jobs were affected. All failed silently with error status and no delivery.

Workaround

Manually edit ~/.openclaw/cron/jobs.json to add the missing to field: "to": "[email protected]"

Suggested Fix

In the cron job creation flow (likely in the API handler or UI form submission), when delivery.channel === "openclaw-weixin" and the request originates from an active weixin session, automatically populate delivery.to from the session's chat_id / user_id.

This is similar to how the accountId is correctly auto-populated in some cases — the to field should follow the same pattern.

Environment

• OS: Linux 6.8.0-100-generic (x64)
• Node: v24.14.0
• OpenClaw: v2026.4.26
• Channel: openclaw-weixin