{"version":"2.1.323","anchor":"workflow-closing-rows-telemetry-now-needs-a-mode-check-befor","canonical_anchor":"workflow-closing-rows-telemetry-now-needs-a-mode-check-befor","heading":"Final workflow progress rows need one more condition before they are kept","tier":"soon","area":"Workflows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/workflow-closing-rows-telemetry-now-needs-a-mode-check-befor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Final workflow progress rows need one more condition before they are kept\n\nA finished local workflow keeps its last progress rows only when a mode check also passes, on top of the off-by-default switch\n\n**What**\n\nA workflow is a scripted multi-step task Claude Code runs. When a local workflow ends, its last progress rows can be kept with its final record. That now needs an extra mode check to pass as well as the switch `tengu_rippling_orbit`. Before, the switch alone was enough, as long as the workflow's script was not being withheld.\n\nThe switch is off unless it is turned on remotely. In readings taken before this release, it was off for this site's account and for a signed-out baseline. Claude Code also now notes when rows were left out or some agent details were dropped.\n\n**Why**\n\nWith the switch off by default and a second condition added, most people will not see these rows kept.\n\n- Flag `tengu_rippling_orbit`: Off in both readings (read for one account on one subscription tier against v2.1.323; this account: off, anonymous baseline: off, 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: Workflows\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}