# Notenik 16.7.3 Available for Beta Testing on April 17th, 2025

**URL:** https://discourse.notenik.app/t/notenik-16-7-3-available-for-beta-testing-on-april-17th-2025/705
**Category:** Beta Versions
**Created:** [April 17, 2025, 9:45pm UTC](https://discourse.notenik.app/t/notenik-16-7-3-available-for-beta-testing-on-april-17th-2025/705 "2025-04-17T21:45:44Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![hbowie](https://discourse.notenik.app/user_avatar/discourse.notenik.app/hbowie/32/6_2.png) [@hbowie](https://discourse.notenik.app/u/hbowie)
#### Post date: [April 19, 2025, 5:54pm UTC](https://discourse.notenik.app/t/notenik-16-7-3-available-for-beta-testing-on-april-17th-2025/705/3 "2025-04-19T17:54:18Z")

</div>

Check out the [latest beta](https://discourse.notenik.app/t/notenik-16-7-4-available-for-beta-testing-on-april-19th-2025/706), which should fix this problem.

The fix is to save the note and refresh the display(s), so the new note is visible.

(I’d had a previous complaint about a user’s input simply being discarded when something like this happens, so Notenik was modified some time ago to save the in-progress note, even if the user has not explicitly requested a save.)

Thanks for reporting this. I think I’d seen some similar behavior myself, but hadn’t taken the time to track it down before now.

I believe something similar would also have happened if the user was changing key fields of an existing note.

Let me know how this works for you!

Thanks again!

---

_[View the full topic](https://discourse.notenik.app/t/notenik-16-7-3-available-for-beta-testing-on-april-17th-2025/705)._