In my experience, notifications failed to update, requiring me to uninstall and reinstall the module. While this process should theoretically work, it doesn’t in practice. This might be manageable in a small, single-user setup, but when scaling to thousands of users across multiple modules, the update method becomes highly impractical and inefficient.

After attempting an update, the system only displayed errors and was completely empty, as described in [this issue](https://unacms.com/d/error-notification-after-upgrade-to-rc1). I had to manually remove the modules, re-download them, and reinstall via **Apps Market > Modules > Updates**. This occurred even on a fresh installation of version 14.B2, indicating that modules still need to be manually updated, akin to the outdated method used in Dolphin.

This update strategy is unsuitable for production environments, as the risk of causing downtime is alarmingly high, close to 99%. While it might suffice for testing or development environments, it is far from a viable solution for live, large-scale systems. It may take years before this update mechanism becomes reliable in real-world scenarios, especially with frequent 500 errors due to unresolved code github issues, as noted [here](https://github.com/unacms/una/issues) and many more in discussion here on UNA. For now, live updates remain an aspiration for the future.