{"version":"2.1.246","anchor":"undelivered-cloud-workspace-changes-get-their-own-message","canonical_anchor":"undelivered-cloud-workspace-changes-get-their-own-message","heading":"Undelivered cloud workspace changes get their own message","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/undelivered-cloud-workspace-changes-get-their-own-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Undelivered cloud workspace changes get their own message\n\nA cloud change that never arrived now gets its own message instead of a generic fetch failure.\n\n**What**\n\nWhen a change never reached the cloud session, you now get a line saying so and the per-turn changes as a fallback, instead of the generic \"Couldn't fetch workspace changes\". The new case is checked before the older text matching for disconnected and not-connected states.\n\n**Evidence**\n\n`not_delivered`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}