{"version":"2.1.246","anchor":"cloud-sessions-can-post-a-status-notice-into-the-transcript","canonical_anchor":"cloud-sessions-can-post-a-status-notice-into-the-transcript","heading":"Cloud sessions can post a status notice into the transcript","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/cloud-sessions-can-post-a-status-notice-into-the-transcript","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Cloud sessions can post a status notice into the transcript\n\nCloud sessions can post status notices into your transcript, such as syncing having been abandoned.\n\n**What**\n\nA new kind of system message, `cloud_session_status`, lets a cloud session report on itself in the conversation at a \"notice\" level with a link. One such notice fires when directory syncing aborts, telling you the cloud session never picked up anything synced from this directory and this session will stop syncing.\n\n**Details**\n\n- The message carries an entry, a URL and a level of `notice`, and has its own renderer.\n- Like the existing bridge status message, it is filtered out of the saved message list, so it shows in the live transcript but is not persisted.\n\n**Evidence**\n\n`The cloud session never picked up anything synced from this directory`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}