{"version":"2.1.319","anchor":"session-list-no-longer-blocks-stop-or-delete-for-sessions-in","canonical_anchor":"session-list-no-longer-blocks-stop-or-delete-for-sessions-in","heading":"Session list no longer explains why a session in another terminal cannot be stopped","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/session-list-no-longer-blocks-stop-or-delete-for-sessions-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Session list no longer explains why a session in another terminal cannot be stopped\n\nTrying to stop or delete a session running in another terminal no longer shows a message saying why\n\n**Unclear.** It is not clear whether stopping or deleting such a session is now refused silently or allowed in cases that were wrongly blocked before.\n\n**What**\n\nIn the session list, trying to stop or delete a session that is running in another terminal used to show a message saying it could not be done for that reason. That message has been removed. For sessions not run by the background service, the action now does nothing and shows nothing.\n\n**Why**\n\nIf the action is refused, you no longer get any feedback saying so.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}