[FEATURE] Re-enabling a daily scheduled task after its time-of-day has passed triggers an immediate catch-up run (surprising for cron-style expectations)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

TITLE: Re-enabling a daily scheduled task after its time-of-day has passed triggers an immediate catch-up run (surprising for cron-style expectations)

Environment: Claude Code desktop app, Windows 10 Pro 19045. Local scheduled task with cron expression (daily at a fixed hour).

Summary: If a daily task is disabled, and later re-enabled at a moment AFTER its scheduled time-of-day, a run fires immediately upon re-enabling ("catch-up"), instead of waiting for the next scheduled occurrence. Same applies on app launch when an occurrence was missed. This may be by design (missed-run semantics), but it is surprising for cron-minded users and can trigger heavy jobs at unintended times (ours started a 90-minute production job in the evening instead of 11 PM).

Steps to reproduce:

1. Create a daily task at, say, 23:00. Disable it.
2. At 19:26 (same day), re-enable it.
3. A run fires at ~19:26 immediately.

Expected / requested: either (a) document the catch-up semantics prominently in the task UI, (b) offer a per-task toggle "run missed occurrence on enable/launch: yes/no", or (c) default to next-occurrence-only for cron tasks.

Impact: unintended immediate executions of scheduled automations after maintenance windows; users must remember to re-enable only before the scheduled hour.

Proposed Solution

Summary: If a daily task is disabled, and later re-enabled at a moment AFTER its scheduled time-of-day, a run fires immediately upon re-enabling ("catch-up"), instead of waiting for the next scheduled occurrence. Same applies on app launch when an occurrence was missed. This may be by design (missed-run semantics), but it is surprising for cron-minded users and can trigger heavy jobs at unintended times (ours started a 90-minute production job in the evening instead of 11 PM).

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_