{"version":"2.1.246","anchor":"routine-creation-always-documents-the-one-shot-schedule-fiel","canonical_anchor":"routine-creation-always-documents-the-one-shot-schedule-fiel","heading":"Routine creation always documents the one-shot schedule field","tier":"use","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/routine-creation-always-documents-the-one-shot-schedule-fiel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Routine creation always documents the one-shot schedule field\n\nRoutine creation now always offers run_once_at as an alternative to a cron expression.\n\n**What**\n\nThe routine-creation instructions now always list `run_once_at` as an alternative to a cron expression, exactly one of which is required. Claude therefore always knows a routine can fire a single time at a future UTC timestamp and then disable itself.\n\n**Evidence**\n\n`RFC3339 UTC timestamp. Must be in the future. Fires once, then auto-disables.`\n\n- Area: Background Tasks\n- Names: `run_once_at`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}