{"version":"2.1.238","anchor":"auto-react-gains-a-paused-state-and-per-session-ledger","canonical_anchor":"auto-react-gains-a-paused-state-and-per-session-ledger","heading":"Auto-react gains a paused state and per-session ledger","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/auto-react-gains-a-paused-state-and-per-session-ledger","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Auto-react gains a paused state and per-session ledger\n\nResuming a session no longer re-reacts to artifact comments it already handled, and auto-react can be paused.\n\n**What**\n\nAutomatic reactions to comments on artifacts can now report a third status, \"paused\", alongside \"stopped\" and \"armed\", and each session keeps a running record of what it has already reacted to. That record is saved with the session and restored when you resume, so resuming no longer re-reacts to comments handled before.\n\n**Details**\n\n- The per-session record is stored as `artifactAutoReactLedger`, cleared when session state is stripped, and handed back on resume as `resumedArtifactAutoReactLedger`.\n- A matching `artifactAutoReactLedgers` collection is saved and restored everywhere session state is serialised, next to the existing artifact comment monitors.\n- Stopping or resuming now also clears two other pieces of leftover state: swept orphan slugs and a pending resume disclosure.\n- The notice shown when auto-react arms is now decided by whether the last outcome was degraded, rather than by whether the user had previously disarmed it.\n- The session file writer also gained a materialisation event and a field used to repair a truncated tail on the session file.\n\n**Evidence**\n\n`artifactAutoReactLedger`, `artifactAutoReactLedgers`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}