# How do I ensure my draft will be saved when I can no longer see the "save draft for later" button?

**URL:** https://meta.discourse.org/t/how-do-i-ensure-my-draft-will-be-saved-when-i-can-no-longer-see-the-save-draft-for-later-button/385291
**Category:** UX
**Created:** [10 oktober 2025 om 23:22 UTC](https://meta.discourse.org/t/how-do-i-ensure-my-draft-will-be-saved-when-i-can-no-longer-see-the-save-draft-for-later-button/385291 "2025-10-10T23:22:54Z")
**Posts on this page:** 1
**Showing post:** 25

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [2 mei 2026 om 06:10 UTC](https://meta.discourse.org/t/how-do-i-ensure-my-draft-will-be-saved-when-i-can-no-longer-see-the-save-draft-for-later-button/385291/25 "2026-05-02T06:10:29Z")

</div>

If that was the case less than 20 characters would still not be saved and a composer with 2 quotes wouldn’t be saved either. But compared to my example above those work:

Ultimately, the idea was that I wouldn’t have to be able to verify Discourse saving, because it saves automatically all the time. Even with fewer characters or quotes.

My problem is that this doesn’t always work, and I only realize it after I’ve closed the composer and see that the save notification doesn’t appear. By then, everything is already gone. With the previous button, I could see in the modal whether saving was offered, so I knew before the loss if it wouldn’t work and could add something accordingly to reach the threshold for saving.

---

_[View the full topic](https://meta.discourse.org/t/how-do-i-ensure-my-draft-will-be-saved-when-i-can-no-longer-see-the-save-draft-for-later-button/385291)._
