{"version":"2.1.281","anchor":"hooks-runtime-a-scope-is-captured-on-every-dispatch-and-int","canonical_anchor":"hooks-runtime-a-scope-is-captured-on-every-dispatch-and-int","heading":"Hooks runtime: a scope is captured on every dispatch and interface call","tier":"internal","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/hooks-runtime-a-scope-is-captured-on-every-dispatch-and-int","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Hooks runtime: a scope is captured on every dispatch and interface call\n\nThe hooks runtime now captures a scope for each dispatch and interface call and releases it when the call finishes\n\n**Unclear.** The finding does not say what the scope holds or what it changes for someone using hooks.\n\n**What**\n\nIn the hooks runtime, which runs your own code at set points in a session, every dispatch, stream dispatch, interface call and served call that is still running now records a scope. The scope is released when the operation finishes.\n\n**Why**\n\nEach running hooks operation now carries its own scope from start to finish.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}