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
on 2023/12/18 12:20
Change comment:
There is no comment for this version
To version 300.1
edited by Carlijn Kokkeler
on 2023/12/21 13:35
on 2023/12/21 13:35
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -11,39 +11,38 @@ 11 11 12 12 == **Feedback Items** == 13 13 14 +//__Runtime overview__// 15 +We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview. 16 + 17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 18 + 14 14 //__Missing properties overview__// 15 15 The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 16 16 17 17 ADD FIGURE 18 18 19 -//__ Containerversionoverview__//20 - Dueto the improvedbuildprocess for containers,the releaseversionsandcontainerversionswill not longer bethe same anymore.Therefore we introduce awaywhere you can look up tosee which containerversionsarelinkedtoa specific release.This can helpyouto identify if yourcontainers that areunninghavetheightversion according tothelease.24 +//__Breaking changes pop-up__// 25 +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'. 21 21 22 -[[image:Main.Images.Release Blog.WebHome@release-blog-21 0-deployment-delights-container-overview.png]]27 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]] 23 23 24 -//__ Improveddeploymentprocess__//25 - The improved release build process, as mentionedabove, bringsanothermajor improvement to the platform. Because container versions will notbeupdatedregularly wean identifyduring a deploymentwhich containershouldget a new containerversion.Onlytheones that should geta new version will be deployed and restarted, all other containerswill not godownand keep running. Thisdecreases the deployment timeand improvesthe performance.29 +//__Broker queue metrics dashboards__// 30 +It is now possible to select the MQTT broker in the queue metrics dashboards. 26 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 -//__ Runtimemetricsprocessing__//33 - The collection and publishingofruntime metrics isnolonger synchronized acrosscontainers,which improves theirprocessing.34 +//__Deployment execution error message__// 35 +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 -//__ Deploymentplan__//36 - Wesolveda bugwhere adeploymentstepintheexecutionofthedeploymentplancould randomly getstuck.37 +//__Cloud template upgrade unjust rollback__// 38 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3. 37 37 38 -//__ Viewallstoreitems__//39 - Anissuehasbeenfixedwhereitwasnotpossibletoload morestoreitemsintheleft panelinhe CreatephaseFlowDesigner.40 +//__Missing log entries__// 41 +We improved crash handling so that log messages clearly show when and why a container failed to start. 40 40 41 -//__ Outofmemorybehavior__//42 -We i mprovedtheoutof memory behaviorofruntimes.Runtimes willnowalwaysrestart whenanoutof memory erroroccurs.43 +//__Runtime logging__// 44 +We fixed a bug where no new log messages were showing up, even though they were produced by the container. 43 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: