{"version":"2.1.246","anchor":"quitting-a-cloud-session-tells-you-what-was-never-delivered","canonical_anchor":"quitting-a-cloud-session-tells-you-what-was-never-delivered","heading":"Quitting a cloud session tells you what was never delivered","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/quitting-a-cloud-session-tells-you-what-was-never-delivered","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Quitting a cloud session tells you what was never delivered\n\nQuitting a cloud session makes one last send attempt and prints anything undelivered.\n\n**What**\n\nOn exit, held messages get one final flush attempt with a 100ms retry budget, and anything that still did not make it is printed as a summary rather than vanishing silently.\n\n**Details**\n\n- Undelivered messages read \"not sent: the cloud session had not yet received this machine's files or settings when you quit.\"\n- The summary also lists per-reason refusals and messages whose delivery was never confirmed, and is worded for one or several (\"Your last message\" \/ \"Your last N messages\").\n- Reachable in any terminal-attached cloud session.\n\n**Evidence**\n\n`not sent: the cloud session had not yet received this machine's files or settings when you quit.`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}