{"version":"2.1.234","anchor":"auto-titled-cloud-sessions-no-longer-count-as-a-unique-name-","canonical_anchor":"auto-titled-cloud-sessions-no-longer-count-as-a-unique-name-","heading":"Auto-titled cloud sessions no longer count as a unique name match","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/auto-titled-cloud-sessions-no-longer-count-as-a-unique-name-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Auto-titled cloud sessions no longer count as a unique name match\n\nMessaging a session by name no longer lands on an arbitrary \"untitled session\".\n\n**What**\n\nCloud and bridge sessions with an empty or auto-generated title, such as \"untitled session\", are now flagged as such in the session list, and sending a message by name refuses to treat one of them as an exact unique match. This stops a message going to an arbitrary untitled session.\n\n**Evidence**\n\n`derivedName`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}