Changes for page 237 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 172.1
edited by Carlijn Kokkeler
on 2023/12/21 16:06
on 2023/12/21 16:06
Change comment:
There is no comment for this version
To version 173.1
edited by Carlijn Kokkeler
on 2023/12/21 16:12
on 2023/12/21 16:12
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -4,21 +4,16 @@ 4 4 5 5 =====New features===== 6 6 7 -* Deploy - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots of the release in the Deploy phase. 8 8 8 + 9 9 =====Minor changes===== 10 10 11 -* Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 12 -* Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images. 11 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start. 13 13 13 + 14 + 14 14 ====Bug fixes==== 15 15 16 -* Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 17 -* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. (#1100) 18 -* Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 19 -* Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck. 20 -* Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 21 -* Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives. 22 -* Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 23 23 24 24 19 +