{"version":"2.1.323","anchor":"one-time-croncreate-refused-on-self-hosted-runners-in-favour","canonical_anchor":"one-time-croncreate-refused-on-self-hosted-runners-in-favour","heading":"One-time scheduled jobs can be refused on self-hosted runners","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/one-time-croncreate-refused-on-self-hosted-runners-in-favour","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### One-time scheduled jobs can be refused on self-hosted runners\n\nOn self-hosted runners, CronCreate can refuse a one-time job and tell Claude to use a connector reminder tool instead\n\n**What**\n\nCronCreate is the tool Claude uses to schedule a job. When a session runs on a self-hosted runner (a machine you manage, which may stop the process), CronCreate can now refuse a one-time job with \"Not scheduled. This session runs on a self-hosted runner\". It then tells Claude to use a connector's reminder tool, which keeps the reminder on the server instead.\n\nThis is off unless it is switched on remotely.\n\n**Why**\n\nA one-time job on a runner that may stop could quietly never run. A reminder kept on the server still fires.\n\n- Flag `tengu_snug_crystal`: Not enough to say (read for one account on one subscription tier against v2.1.323; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Self-Hosted Runners\n- Names: `CronCreate`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: yes"}