Bug Description

Cron jobs with sessionTarget: isolated fail to execute. The task status remains stuck in running state, but no actual execution occurs and no run history is recorded.

Steps to Reproduce

1. Create a cron job with isolated session:

openclaw cron add --name "Test" --cron "00 15 * * *" --session isolated --message "Test task" --agent news-agent --channel feishu --to "user:ou_xxx"

2. Check job status:

openclaw cron list

3. Observe: Status shows running but Last column is empty (-)

4. Check run history:

openclaw cron runs --id <jobId>

5. Result: Empty (no execution records)

Expected vs Actual

Key Log Entry

"cron: clearing stale running marker on startup"

Environment

• OpenClaw: 2026.4.11
• OS: macOS 24.6.0
• Node: v24.2.0

Workaround

Use sessionTarget: main instead of isolated.

Happy to provide additional logs if needed!