{"version":"2.1.288","anchor":"remote-backend-conflict-error-is-rebuilt-without-the-error","canonical_anchor":"remote-backend-conflict-error-is-rebuilt-without-the-error","heading":"Remote option conflict messages lose their Error: prefix","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/remote-backend-conflict-error-is-rebuilt-without-the-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remote option conflict messages lose their Error: prefix\n\nMessages about combining two options that both pick a remote backend no longer start with \"Error: \" in their text\n\n**Unclear.** It is not clear whether \"Error: \" is now added elsewhere, so the message you see may look the same.\n\n**What**\n\nWhen you combine two command-line options that both choose a remote backend, meaning where a session runs, the message is now built differently. It ends with \"both select a remote backend; pick one.\" The leading \"Error: \" has been removed from the message text.\n\n**Why**\n\nThe wording of these error messages has changed slightly.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}