openclaw - 💡(How to fix) Fix Bug: Cron job execution timeout with isolated sessionTarget [2 comments, 2 participants]

Official PRs (…)
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.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#43721Fetched 2026-04-08 00:17:28
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
commented ×2closed ×1locked ×1

Error Message

"lastError": "Error: cron: job execution timed out"
"lastDurationMs": 30060

Fix Action

Workaround

Direct subagent spawning works fine (3 seconds), only cron with isolated mode fails.

Code Example

"lastError": "Error: cron: job execution timed out"
"lastDurationMs": 30060
RAW_BUFFERClick to expand / collapse

Bug Description

Cron jobs with sessionTarget: isolated always timeout after 30 seconds.

Error

"lastError": "Error: cron: job execution timed out"
"lastDurationMs": 30060

Steps to Reproduce

  1. Create a cron job with delivery channel
  2. Set sessionTarget to "isolated"
  3. Run the job manually
  4. Job stays in "running" state and times out

Environment

  • OpenClaw 2026.3.8
  • Platform: Linux WSL2

Workaround

Direct subagent spawning works fine (3 seconds), only cron with isolated mode fails.

extent analysis

Fix Plan

The fix involves increasing the timeout for cron jobs with sessionTarget: isolated.

Steps to Fix

  • Increase the cron job timeout by setting the executionTimeout property.
  • Update the cron job configuration to include the new timeout value.

Example Code

// Update cron job configuration
const cronJobConfig = {
  // ... existing config ...
  sessionTarget: 'isolated',
  executionTimeout: 120000, // 2 minutes in milliseconds
};

// Alternatively, update the cron job using the OpenClaw API
openclaw.cron.updateJob(jobId, {
  executionTimeout: 120000,
});

Verification

  • Run the cron job manually and verify that it completes without timing out.
  • Check the lastDurationMs value in the job logs to ensure it's within the new timeout limit.

Extra Tips

  • Consider monitoring cron job execution times to detect potential issues before they cause timeouts.
  • Adjust the executionTimeout value based on the specific requirements of your cron jobs.

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?
Loading…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING