Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Remove or improve CronCreate tool - creates unreliable session-only cron jobs

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…

Error Message

  • Provide no execution logs or error tracking
  • Jobs fail silently with no error messages
  • ✅ Proper error handling
  • Add proper error handling and logging
  • Warn users that jobs are session-only

Root Cause

Today I scheduled a cron job to send an email at 1:45 PM:

  • Created: 1:34 PM via CronCreate
  • Expected execution: 1:45 PM
  • Actual result: Never executed
  • Evidence: No email sent, no logs, no errors
  • Root cause: Session-only job failed silently

Fix Action

Fix / Workaround

Workaround: Use mcp__myclaw__scheduler_upsert_job instead for reliable persistent scheduling.

RAW_BUFFERClick to expand / collapse

Problem Description

The CronCreate tool creates session-only cron jobs that are unreliable and confusing for users. These jobs:

  • Live only in memory during the Claude session
  • Do not persist across session restarts
  • Fail silently when sessions end
  • Are not visible in any scheduler database
  • Provide no execution logs or error tracking
  • Create false expectations about scheduled task reliability

User Impact

Users schedule important tasks (like sending emails) expecting them to execute reliably, but:

  • Jobs fail silently with no error messages
  • No execution history available
  • No way to monitor or debug failures
  • Creates distrust in the scheduling system
  • Wastes user time troubleshooting invisible issues

Actual Example

Today I scheduled a cron job to send an email at 1:45 PM:

  • Created: 1:34 PM via CronCreate
  • Expected execution: 1:45 PM
  • Actual result: Never executed
  • Evidence: No email sent, no logs, no errors
  • Root cause: Session-only job failed silently

Better Alternative

The MyClaw Scheduler (via mcp__myclaw__scheduler_upsert_job) provides:

  • ✅ Persistent jobs across sessions
  • ✅ Execution history tracking
  • ✅ Retry logic for failures
  • ✅ Visible in scheduler database
  • ✅ Proper error handling
  • ✅ Job monitoring and management

Suggested Solutions

Option 1: Remove CronCreate entirely

  • Remove the unreliable tool completely
  • Direct users to use proper scheduler systems
  • Prevent confusion and failures

Option 2: Improve CronCreate significantly

  • Make jobs persistent by default
  • Add proper error handling and logging
  • Show warnings about session-only nature
  • Integrate with existing scheduler databases
  • Add execution monitoring
  • Provide failure notifications

Option 3: Add clear warnings

  • Warn users that jobs are session-only
  • Suggest alternatives for persistent jobs
  • Document limitations clearly
  • Add failure detection and notifications

Reproduction Steps

  1. Use CronCreate to schedule a task
  2. Wait for scheduled time
  3. Observe: Task never executes
  4. Check: No logs, no errors, no evidence

Expected Behavior

Scheduled tasks should:

  • Execute reliably at scheduled times
  • Provide execution confirmation
  • Log successes and failures
  • Survive session restarts
  • Be monitorable and debuggable

Environment

  • Claude Code (latest version)
  • CronCreate tool
  • Session: 2026-04-20
  • Timezone: Asia/Calcutta (IST)

Priority

High - This affects user trust in scheduling functionality and causes silent failures of important tasks.

Workaround: Use mcp__myclaw__scheduler_upsert_job instead for reliable persistent scheduling.

extent analysis

TL;DR

The most likely fix is to use the mcp__myclaw__scheduler_upsert_job API for creating persistent and reliable cron jobs instead of the CronCreate tool.

Guidance

  • Identify and avoid using CronCreate: Recognize the limitations and unreliability of CronCreate for scheduling important tasks due to its session-only nature and lack of error handling or logging.
  • Migrate to mcp__myclaw__scheduler_upsert_job: Utilize the mcp__myclaw__scheduler_upsert_job API for creating cron jobs as it provides persistent jobs, execution history, retry logic, and proper error handling.
  • Document limitations of CronCreate: If CronCreate cannot be immediately removed or improved, ensure that its limitations are clearly documented and communicated to users to set appropriate expectations.
  • Monitor and provide feedback: Implement monitoring for jobs created with mcp__myclaw__scheduler_upsert_job and provide feedback mechanisms to users about job execution status to build trust in the scheduling system.

Example

No specific code example is provided due to the nature of the issue focusing on the tool's functionality rather than a specific code snippet. However, replacing CronCreate with mcp__myclaw__scheduler_upsert_job in scheduling workflows is the key step.

Notes

The provided workaround using mcp__myclaw__scheduler_upsert_job is a reliable alternative but may require adjustments in how users interact with the scheduling system. It's essential to evaluate the impact of completely removing CronCreate or improving it significantly based on user needs and system requirements.

Recommendation

Apply the workaround by using mcp__myclaw__scheduler_upsert_job for all new scheduling tasks to ensure reliability and persistence, as it addresses the core issues with CronCreate and provides a more robust scheduling solution.

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…
#file not found#serialization error#model compatibility#GPU setup#container setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING