{"version":"2.1.251","anchor":"clear-message-when-resuming-a-session-that-is-still-running","canonical_anchor":"clear-message-when-resuming-a-session-that-is-still-running","heading":"Clear message when resuming a session that is still running","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/clear-message-when-resuming-a-session-that-is-still-running","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Clear message when resuming a session that is still running\n\nResuming a session that is still running now offers to attach, stop or fork it.\n\n**What**\n\nTrying to resume or fork a session that is currently running as a background session now explains the situation and gives the options: attach to it, stop it, or fork a copy. Previously this surfaced as a generic error.\n\n**Details**\n\n- Triggered whenever the target session is detected as an active background job. Available to everyone, no flag.\n\n**Evidence**\n\n`That session is still running as a background session`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}