{"version":"2.1.251","anchor":"session-registry-can-now-be-watched-for-state-changes","canonical_anchor":"session-registry-can-now-be-watched-for-state-changes","heading":"Session registry can now be watched for state changes","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/session-registry-can-now-be-watched-for-state-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Session registry can now be watched for state changes\n\nLong-lived session state can now be watched, likely plumbing for a status indicator.\n\n**What**\n\nThe registry that tracks long-lived sessions gained a way to subscribe to a session's state, polling and emitting normalized values such as an armed state naming the engine and direction, or an off state naming the reason. It also counts when a session's full listing grows past its allowed size. Nothing user-visible consumes it yet; it looks like plumbing for a status indicator.\n\n**Details**\n\n- The polling interval is set by an internal constant whose value is not visible in the build.\n\n**Evidence**\n\n`wholeListingOutgrew`\n\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}