Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 292.1
edited by Carlijn Kokkeler
on 2023/12/18 12:20
Change comment: There is no comment for this version
To version 295.1
edited by Carlijn Kokkeler
on 2023/12/18 12:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,34 +16,14 @@
16 16  
17 17  ADD FIGURE
18 18  
19 -//__Container version overview__//
20 -Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
19 +//__Broker queue metrics dashboards__//
20 +It is now possible to select the MQTT broker in the queue metrics dashboards.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
23 -
24 -//__Improved deployment process__//
25 -The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
26 -
27 -//__Rebuilding of images__//
28 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
29 -
30 30  == **Bug Fixes** ==
31 31  
32 -//__Runtime metrics processing__//
33 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
24 +//__Deployment execution error message__//
25 +In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup.
34 34  
35 -//__Deployment plan__//
36 -We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
37 -
38 -//__View all store items__//
39 -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.
40 -
41 -//__Out of memory behavior__//
42 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
43 -
44 -//__Max fetch size__//
45 -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.
46 -
47 47  == **Fancy Forum Answers** ==
48 48  
49 49  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: