{"version":"2.1.248","anchor":"self-pacing-loop-wakeups-no-longer-blocked-by-a-runtime-swit","canonical_anchor":"self-pacing-loop-wakeups-no-longer-blocked-by-a-runtime-swit","heading":"Self-pacing \/loop wakeups no longer blocked by a runtime switch","tier":"notice","area":"Loop","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/self-pacing-loop-wakeups-no-longer-blocked-by-a-runtime-swit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Self-pacing \/loop wakeups no longer blocked by a runtime switch\n\nLong-running \/loop can schedule its own wake-ups now that the server switch check is gone.\n\n**What**\n\nThe tool that lets a long-running `\/loop` schedule its own next wake-up used to refuse and log a `gate_off` event when a server-side switch was off. That check is gone, so the tool works for anyone who can call it, and it now only declines once the loop has hit its maximum duration.\n\n**Details**\n\n- The refusal text no longer mentions the switch; the remaining refusal cites max duration only and tells the model not to re-issue.\n- No setting replaces the removed check.\n\n**Evidence**\n\n`Wakeup not scheduled. The loop reached its maximum duration \u2014 the loop has ended; do not re-issue.`\n\n- Area: Loop\n- Names: `\/loop`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}