{"version":"2.1.246","anchor":"plugins-can-cancel-the-running-turn-up-to-50-times-a-session","canonical_anchor":"plugins-can-cancel-the-running-turn-up-to-50-times-a-session","heading":"Plugins can cancel the running turn, up to 50 times a session","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/plugins-can-cancel-the-running-turn-up-to-50-times-a-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Plugins can cancel the running turn, up to 50 times a session\n\nA plugin hook can now cancel the running turn, once every two seconds and fifty times per session.\n\n**What**\n\nA plugin hook can now stop the turn that is currently running by calling `$.turn.abort({ turnId })`. Each plugin is limited to one abort every 2000ms, and the whole session is capped at 50 aborts.\n\n**Details**\n\n- The call is refused when no turn is running, when the id given is not the running turn, and when that turn is already ending.\n- The two ceilings are named `TURN_ABORT_SESSION_COUNT` (50) and `TURN_ABORT_MIN_INTERVAL_MS` (2000).\n- A successful abort writes a line into the plugin UI log, so a turn cut short by a plugin is attributable.\n- Part of the host operation table rather than a separately flagged feature.\n\n**Evidence**\n\n`TURN_ABORT_MIN_INTERVAL_MS`\n\n- Area: Plugins\n- Names: `$.turn.abort`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5"}