Skip to Content

Changes for page 256 - Power Up

Last modified by Erik Bakker on 2025/11/04 12:44
From version 289.2
edited by Erik Bakker
on 2025/11/04 12:44
Change comment: There is no comment for this version
To version 184.1
edited by CarlijnKokkeler
on 2024/01/15 14:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -256 - Power Up
1 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,15 +1,27 @@
1 -This release features various updates to our platform, with a user-centric focus, as we work on improved functionality for our new event streaming broker and API Gateway. All those improvements will be shared in the future once everything is ready. Additionally, we want to raise awareness that several new **[[environment templates>>> Main.Release Information.Cloud Templates.WebHome||target="blank"]]** have been released that need to be updated before **December, 14th**. So if you have yet to update please take the necessary actions.
1 +In the last sprint cycle, we focused on ....
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.256 - Power Up.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Feedback Fiesta||target="blank"]].
4 4  
5 -==== Bug fixes ====
5 +=====New features=====
6 6  
7 -* Design - System Message: Improved performance of saving entities whith a large number of attributes. (#1731)
8 -* Design - Store: Two fixes on importing store items for synchronous messages. (#1579)
9 -** From store functionality for API Gateway is restored.
10 -** Additionally, users can import store item to synchronous system message - response message.
11 -* Design - Create - System Message (API integrations) - The request system message correctly displays the message definition (#1713)
12 -* Create - Add Integrations: We have fixed a bug where some Mendix systems could face an error when trying to add an event streaming integration in Create.
13 -* Deploy - Containers: Debug icon has on hover text (#1725)
14 -* Manage - Alerting: Partial words from an alert's description can be searched and still return accurate results. (#1726)
7 +* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
8 +* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
15 15  
10 +=====Minor changes=====
11 +
12 +* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
13 +* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
14 +* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
15 +* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917)
16 +* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
17 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
18 +
19 +====Bug fixes====
20 +
21 +* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
22 +* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
23 +* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
24 +* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container.
25 +* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108)
26 +
27 +