{"version":"2.1.246","anchor":"one-off-scheduled-runs-are-always-documented-in-schedule","canonical_anchor":"one-off-scheduled-runs-are-always-documented-in-schedule","heading":"One-off scheduled runs are always documented in \/schedule","tier":"use","area":"Scheduled Runs","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/one-off-scheduled-runs-are-always-documented-in-schedule","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### One-off scheduled runs are always documented in \/schedule\n\n\/schedule now always documents one-time runs and how to re-arm one that already fired.\n\n**What**\n\nThe scheduled-runs command no longer hides one-time runs behind a flag; every session sees that a routine can be scheduled to fire once, and that a run reported as having ended for reason `run_once_fired` can be re-armed by setting a new one-shot time.\n\n**Details**\n\n- The flag that previously gated this, `tengu_mocha_barista`, is gone from the build entirely.\n- The command itself still requires the gate `tengu_surreal_dali` (off unless the server says otherwise), the `allow_remote_sessions` permission, and a non-cloud session.\n\n**Evidence**\n\n`run_once_fired`\n\n- Flag `tengu_mocha_barista`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.246; this account: on, anonymous baseline: on, compiled default: not a boolean we can read)\n- Flag `tengu_surreal_dali`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.246; this account: on, anonymous baseline: on, compiled default: off)\n- Area: Scheduled Runs\n- Names: `\/schedule`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}