Skip to Content

Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 287.1
edited by Carlijn Kokkeler
on 2023/12/04 15:48
Change comment: There is no comment for this version
To version 288.1
edited by Carlijn Kokkeler
on 2023/12/06 08:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,12 +3,12 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
6 +**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7 7  
8 8  == **Alerts** ==
9 9  
10 10  //__Topic approaching max size alert__//
11 -The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
11 +The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
12 12  
13 13  //__Missing metrics alert__//
14 14  We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
... ... @@ -32,7 +32,7 @@
32 32  The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
33 33  
34 34  //__Deployment plan__//
35 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
35 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
36 36  
37 37  //__View all store items__//
38 38  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.
... ... @@ -41,7 +41,7 @@
41 41  We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
42 42  
43 43  //__Max fetch size__//
44 -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.
44 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
45 45  
46 46  == **Fancy Forum Answers** ==
47 47