Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 257.3
edited by Danniar Firdausy
on 2023/11/07 12:45
Change comment: There is no comment for this version
To version 257.4
edited by Danniar Firdausy
on 2023/11/07 12:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -33,8 +33,8 @@
33 33  //__Improved image building performance__//
34 34  We have implemented an improvement on the preparing step of the release at the begining of the deployment, which leads to a faster deployment process.
35 35  
36 -//__Default "errorChannel" on Gen3 migration__//
37 -During a migration of a model to Gen3, we have introduced a check now for flows that did not have custom error handling to be set their error channel to "errorChannel" after the migration if the custom error handling is set to false.
36 +//__Default "errorChannel" on next-generation architecture migration__//
37 +During a migration of a model to the next-generation architecture, we have introduced a check now for flows that did not have custom error handling to be set their error channel to "errorChannel" after the migration if the custom error handling is set to false.
38 38  
39 39  == **Bug Fixes** ==
40 40  
... ... @@ -41,8 +41,8 @@
41 41  //__Incorrect deployed containers__//
42 42  A fix has been implemented to address the issue where older containers were deployed while it was shown that the new ones instead are deployed. This problem was caused by auto-healing that triggered during a new deployment.
43 43  
44 -//__Log messages in Gen3 models__//
45 -We have implemented an improvement in our infra components that is intended to reduce the occurance of log messages failed to be sent in Gen3 models.
44 +//__Log messages in next-generation architecture models__//
45 +We have implemented an improvement in our infra components that is intended to reduce the occurance of log messages failed to be sent in the next-generation architecture models.
46 46  
47 47  //__Random stuck in deployment plan execution__//
48 48  We addressed an issue where the execution of deployment plan would occasionally become stuck or halted unexpectedly.