{"version":"2.1.234","anchor":"precomputed-session-resolution-on-resume-gated-off","canonical_anchor":"precomputed-session-resolution-on-resume-gated-off","heading":"Precomputed session resolution on resume, gated off","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/precomputed-session-resolution-on-resume-gated-off","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Precomputed session resolution on resume, gated off\n\nResume can report which session it resolved against an expected id, but the flag is off.\n\n**What**\n\nResuming a session can now hand in a callback that reports which session was resolved, checked against an expected session id. It is behind the `tengu_hover_rest` flag, which defaults to off, and is skipped when you are forking a session rather than resuming one.\n\n**Details**\n\n- Nothing in this build turns the flag on, so whether it runs is decided by server-side configuration.\n\n**Evidence**\n\n`onSessionResolved`\n\n- Flag `tengu_hover_rest`: Off in both readings (read for one account on one subscription tier against v2.1.234; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Sessions\n- Names: `tengu_hover_rest`\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}