Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 324.1
edited by Carlijn Kokkeler
on 2023/12/21 15:22
Change comment: There is no comment for this version
To version 329.1
edited by Carlijn Kokkeler
on 2024/01/02 15:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,7 +10,7 @@
10 10  We improved crash handling so that log messages clearly show when and why a container failed to start.
11 11  
12 12  //__Runtime logging__//
13 -We fixed a bug where no new log messages were showing up, even though they were produced by the container.
13 +We fixed a bug where no new log messages were showing up, even though they were produced by a container.
14 14  
15 15  //__Deployment execution error message__//
16 16  In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
... ... @@ -18,7 +18,7 @@
18 18  == **Overviews** ==
19 19  
20 20  //__Runtime overview__//
21 -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.
21 +We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
22 22  
23 23  [[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
24 24  
... ... @@ -28,7 +28,7 @@
28 28  [[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
29 29  
30 30  //__Runtime restart or redeploy overview__//
31 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
31 +Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
32 32  
33 33  [[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
34 34  
... ... @@ -40,7 +40,7 @@
40 40  [[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
41 41  
42 42  //__External recipients emailaddress__//
43 -The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
43 +The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
44 44  
45 45  //__Broker queue metrics dashboards__//
46 46  It is now possible to select the MQTT broker in the queue metrics dashboards.
... ... @@ -54,8 +54,8 @@
54 54  //__Message throughput__//
55 55  The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
56 56  
57 -//__Cloud template upgrade unjust rollback__//
58 -An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
57 +//__Cloud template upgrade incorrect rollback__//
58 +An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
59 59  
60 60  //__Next generation block__//
61 61  Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.