{"version":"2.1.227","anchor":"scheduling-surfaces-now-also-require-the-allow-routines-poli","canonical_anchor":"scheduling-surfaces-now-also-require-the-allow-routines-poli","heading":"Scheduling surfaces now also require the allow_routines policy","tier":"notice","area":"Enterprise Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/scheduling-surfaces-now-also-require-the-allow-routines-poli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Scheduling surfaces now also require the allow_routines policy\n\nScheduling now requires the allow_routines policy as well as remote sessions.\n\n**What**\n\nThe cloud and scheduling prompts and the schedule command previously checked only the `allow_remote_sessions` policy setting. They now also check `allow_routines`, so an organisation that permits remote sessions but not routines will no longer be offered scheduling or given the tool.\n\n**Details**\n\n- the `tengu_surreal_dali` flag, off unless the server enables it, still gates all of this on top of both policy settings\n\n**Evidence**\n\n`allow_routines`\n\n- Flag `tengu_surreal_dali`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.227; this account: on, anonymous baseline: on, 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: Enterprise Settings\n- Names: `allow_routines`, `allow_remote_sessions`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}