{"version":"2.1.223","anchor":"interrupting-a-remote-turn-no-longer-fires-the-turn-complete","canonical_anchor":"interrupting-a-remote-turn-no-longer-fires-the-turn-complete","heading":"Interrupting a remote turn no longer fires the turn-complete callback","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/interrupting-a-remote-turn-no-longer-fires-the-turn-complete","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Interrupting a remote turn no longer fires the turn-complete callback\n\nInterrupting a remote turn no longer triggers a completion bell or notification.\n\n**What**\n\nStopping a turn in a remote session no longer produces the completion bell or notification.\n\n**Details**\n\n- The thin-client session hook keeps a counter incremented on user interrupt.\n- On the next result frame the counter is decremented instead of calling `onTurnComplete`.\n- The counter is reset on reconnect.\n- The same guard was added to the other remote session hook.\n\n**Evidence**\n\n`onTurnComplete`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}