Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 09:59
From version 181.1
edited by Carlijn Kokkeler
on 2024/01/02 11:00
Change comment: There is no comment for this version
To version 183.1
edited by Carlijn Kokkeler
on 2024/01/03 10:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -11,7 +11,7 @@
11 11  
12 12  * Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
13 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: Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to 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 15  * Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917)
16 16  * Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
17 17  * Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
... ... @@ -19,7 +19,7 @@
19 19  ====Bug fixes====
20 20  
21 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 unjustly due to failed runtime checks.
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 23  * Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
24 24  * Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container.
25 25  * Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108)