{"version":"2.1.246","anchor":"the-sdk-transport-can-ask-the-main-loop-whether-it-is-still-","canonical_anchor":"the-sdk-transport-can-ask-the-main-loop-whether-it-is-still-","heading":"The SDK transport can ask the main loop whether it is still working","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/the-sdk-transport-can-ask-the-main-loop-whether-it-is-still-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### The SDK transport can ask the main loop whether it is still working\n\nThe SDK transport can now ask the main loop whether it's truly idle before saying so.\n\n**What**\n\nThe transport used by the SDK and bridge gained a way to register a liveness probe, so when the last pending permission or dialog request resolves it announces `idle` rather than `running` if the main loop reports it has nothing to do.\n\n**Details**\n\n- Print\/headless mode registers the probe from its idle gate.\n- If the probe throws, the failure is recorded under the existing `per_task_stop_sparing` event with reason `liveness_probe_throw` and the session is reported as not idle.\n- Present on this build wherever the SDK or bridge transport is used, with no flag.\n\n**Evidence**\n\n`setMainLoopLiveness`\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}