Investigating: Configuration row of copied configurations can not be deleted

2022-01-18 18:15 UTC We're investigating issue, where rows of configuration, which was copied from another configuration cannot be deleted nor updated. 

2022-01-18 18:55 UTC We've identified the issue is related to internal database migration. Only configurations of components with rows, such as DB writers and extractors are affected.

2022-01-18 19:36 UTC We know what causes the problem and we are working on a fix. We will let you know as soon as the fix is deployed.

2022-01-19 9:30 UTC The fix has been deployed. We are sorry for any inconvenience.

2022-01-19 11:32 UTC We're preparing a report with the list of affected configurations and next steps. At the moment, we advise users to delete affected (copied) configurations and create new copy.

2022-01-21 10:32 UTC We have fixed all affected configurations with 'configuration cannot be deleted nor updated' problem.

Unfortunately, we also found a problem with mismatch updated date time between configuration and rows versions. We are working on solution. We are sorry for any inconvenience.

2022-01-24 15:05 UTC All project on have now fixed author and created time of configuration rows versions. 

Rest of platform will be fixed 2022-01-25.

2022-01-25 08:00 UTC and have now fixed author and created time of configuration rows versions.