{"version":"2.1.242","anchor":"loop-ticks-must-report-whether-anything-happened","canonical_anchor":"loop-ticks-must-report-whether-anything-happened","heading":"Loop ticks must report whether anything happened","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/loop-ticks-must-report-whether-anything-happened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Loop ticks must report whether anything happened\n\nSelf-scheduled loops that do nothing now collapse quietly instead of scrolling filler past you.\n\n**What**\n\nA self-scheduled loop tick now has to tell the scheduler whether it changed anything, by passing a `noop` flag set true for a tick that did nothing. Quiet holds collapse in your terminal instead of scrolling past.\n\n**Details**\n\n- Applies to the three continuation prompts used by self-scheduled (non-cron) loops; cron-driven loops are unchanged.\n- The scheduling tool already documented the flag: \"Consecutive `noop: true` ticks are collapsed in the user's terminal view and tracked as a streak.\"\n\n**Evidence**\n\n`and \\`noop\\` set to \\`true\\` if this tick changed nothing (or \\`false\\` if it did)`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}