{"version":"2.1.248","anchor":"background-session-start-errors-can-be-withheld","canonical_anchor":"background-session-start-errors-can-be-withheld","heading":"Background-session start errors can be withheld","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/background-session-start-errors-can-be-withheld","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Background-session start errors can be withheld\n\nFailing to fork work into the background may show a fixed message instead of the real error.\n\n**What**\n\nWhen the confirm dialog for forking work into the background fails to start the session, some connections now show a fixed message instead of the underlying error text.\n\n**Details**\n\n- The message is \"Couldn't start the background session (detail withheld on this connection).\"\n- Which connections redact is decided by a check on the connection type; the helper behind that check is not resolved in this build.\n\n**Evidence**\n\n`Couldn't start the background session (detail withheld on this connection).`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}