openclaw - ✅(Solved) Fix Bug: Cron Job delivery channel defaults to 'last' instead of valid channel [1 pull requests, 1 comments, 2 participants]

openclaw2026-03-23 07:37:09

ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#52706•Fetched 2026-04-08 01:20:03

View on GitHub

Comments

Participants

Timeline

Reactions

Author

DY991dy

Participants

DY991dy

Hollychou924

Timeline (top)

cross-referenced ×2commented ×1subscribed ×1unsubscribed ×1

Root Cause

Root Cause: The "last" value means "use the last successfully sent channel" and relies on session history. For newly created cron jobs without a session history, lastChannel resolves to undefined, causing delivery to fail.

Code Example

"Delivering to Feishu requires target <chatId|user:openId|chat:chatId>"

RAW_BUFFERClick to expand / collapse

Bug: Cron Job delivery channel defaults to "last" instead of valid channel

Description: When creating a new Cron Job via OpenClaw control UI, the delivery.channel field defaults to "last" which causes delivery failure for new jobs that have no previous session history.

Steps to reproduce:

Open OpenClaw dashboard → Cron Jobs
Click "New Job"
Fill in job details (name, schedule, payload)
Check the delivery configuration (usually kept as default)
Save and check ~/.openclaw/cron/jobs.json
See "channel": "last" instead of a valid channel ID

Expected: New jobs should default to a valid channel ID or show a warning that no channel is selected.

Actual: Channel defaults to "last" which fails with:

"Delivering to Feishu requires target <chatId|user:openId|chat:chatId>"

Code locations:

ui/src/ui/app-defaults.ts - defaults deliveryChannel: "last" and failureAlertChannel: "last"
ui/src/ui/views/cron.ts:957 - form .value=${props.form.deliveryChannel || "last"}
src/infra/outbound/targets.ts:135 - "last" resolution: let channel = requestedChannel === "last" ? lastChannel : requestedChannel;

Version:

OpenClaw: v2026.3.13-1
Node: v24.13.1
macOS: Darwin 24.3.0

Suggested Fix Options:

Option 1: Change the default to an empty string and show a validation warning if no channel is selected
Option 2: Auto-populate with the most recently used channel from existing jobs
Option 3: Add a dropdown that only shows valid channel IDs (excluding "last") for new jobs

Additional context: This affects all newly created cron jobs from the UI, making them fail to deliver results without manual intervention to fix the channel value.

extent analysis

Fix Plan

To fix the issue, we will implement Option 1: Change the default to an empty string and show a validation warning if no channel is selected.

Step-by-Step Solution:

Update defaults: In ui/src/ui/app-defaults.ts, change the default deliveryChannel value to an empty string:

deliveryChannel: "",

2. **Modify form value**: In `ui/src/ui/views/cron.ts:957`, update the form value to use the new default:
   ```typescript
.value=${props.form.deliveryChannel || ""}

Add validation warning: In ui/src/ui/views/cron.ts, add a validation check to display a warning if no channel is selected:

if (!props.form.deliveryChannel) { console.warn("No delivery channel selected. Please choose a valid channel."); // Display warning to user }

4. **Update channel resolution**: In `src/infra/outbound/targets.ts:135`, keep the existing logic to resolve the `"last"` channel value, but add a check to handle the new default empty string value:
   ```typescript
let channel = requestedChannel === "last" ? lastChannel : requestedChannel;
if (!channel) {
  throw new Error("No valid delivery channel selected.");
}

Verification

To verify the fix, create a new cron job and check that:

The deliveryChannel field is empty by default.
A validation warning is displayed if no channel is selected.
The job fails with a clear error message if no valid channel is selected.

Extra Tips

Consider implementing Option 2 or Option 3 for a more user-friendly experience.
Review existing cron jobs to ensure they have a valid deliveryChannel value.
Test the fix thoroughly to ensure it works as expected in different scenarios.

Vote matrix · Quick signals

Works

Did the solution work? Tap to confirm.

Easy Fix

Was it a quick fix?

Time Saver

Did it save you time?

Blocking

Was it severely blocking?

Common Issue

Are others likely hitting this too?

Flaky / Intermittent

Is it intermittent?

Verified / Reproducible

Can you reproduce it reliably?

#memory management #API rate limit #retriever error #indexing error #inference speed

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

openclaw - ✅(Solved) Fix Bug: Cron Job delivery channel defaults to 'last' instead of valid channel [1 pull requests, 1 comments, 2 participants]

Recommended Tools

GitHub issue graph ai analysis

Root Cause

Fix Action

Fixed

PR fix notes

PR #52769: Fix Cron delivery channel defaults for new jobs

Description (problem / solution / changelog)

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

User-visible / Behavior Changes

Security Impact (required)

Repro + Verification

Environment

Steps

Expected

Actual

Evidence

Human Verification (required)

Review Conversations

Compatibility / Migration

Failure Recovery (if this breaks)

Risks and Mitigations

Changed files