{"version":"2.1.299","anchor":"croncreate-one-shot-jitter-computation-passes-oneshot","canonical_anchor":"croncreate-one-shot-jitter-computation-passes-oneshot","heading":"One-time scheduled task previews now use the one-time timing rule","tier":"notice","area":"Scheduled Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/croncreate-one-shot-jitter-computation-passes-oneshot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### One-time scheduled task previews now use the one-time timing rule\n\nThe next-run preview for scheduled tasks that run only once is now worked out as a one-time job\n\n**What**\n\nThe `CronCreate` tool lets Claude Code schedule tasks. When it shows when a task that runs only once will next run, it now tells the scheduler that the job is a one-time job. Before, the preview was worked out without that information.\n\nThe stock description of `CronCreate` that Claude Code gives the model also changed wording in the capture taken under this release.\n\n**Why**\n\nThe way the scheduler adds a small timing offset to jobs changed, and the preview for one-time jobs now follows the same rule.\n\n- Area: Scheduled Tasks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}