Skip to Content

Changes for page 264 - Strict Separation

Last modified by Erik Bakker on 2026/03/22 21:45
From version 322.1
edited by Erik Bakker
on 2026/03/22 21:39
Change comment: There is no comment for this version
To version 325.1
edited by Erik Bakker
on 2026/03/22 21:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,6 @@
1 1  This release includes our new user management for models running on our latest versions of the API Gateway **and** Event Streaming offerings. Furthermore, it includes a new **[[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** that improves machine behavior in a single-lane cloud configuration when runtimes are added or removed. On top of that, we introduce several improvements that enhance and clarify the user experience throughout the platform.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.264 - Strict Seperation.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.264 - Strict Separation.WebHome||target="blank"]].
4 4  
5 5  ==== Minor changes ====
6 6  
... ... @@ -13,6 +13,7 @@
13 13  ** If any runtimes in the list of linked runtimes do not use the property, we suggest removing those runtimes from the list.
14 14  ** If none of the linked runtimes use the property, we recommend removing it.
15 15  * Deploy - Releases: It is no longer possible to try to deploy a release that contains runtimes that are not linked to any flows in the architecture. (#1066)
16 +* Deploy - Architecture: Adding/moving/deleting containers from machines will now not replace the underlying instances. This was only the case for singlelanes. Doublelanes do not have this behaviour and are not affected.
16 16  
17 17  ==== Bug fixes ====
18 18