{"version":"2.1.238","anchor":"storage-handle-passed-into-many-more-call-paths","canonical_anchor":"storage-handle-passed-into-many-more-call-paths","heading":"Storage handle passed into many more call paths","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/storage-handle-passed-into-many-more-call-paths","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Storage handle passed into many more call paths\n\nResume, remote sessions and several other paths now get an explicit storage handle instead of a global.\n\n**What**\n\nSession resume and lookup, the fullscreen boot check, remote session creation, background and remote agent resume, login profile saving, the SDK stream transport and the upsell notification path now all take an explicit storage handle instead of reaching for a global. This decides which storage backend each operation writes to, not what it does.\n\n**Details**\n\n- Remote session creation also sends the storage handle and a `settings_gate` telemetry field.\n\n**Evidence**\n\n`storageV5`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}