Hallo wereld,

We have discovered an issue on redundancy group configuration and it is very reproducible any time in any DMS.
In a DM redundancy group configuration of two elements (a main and a backup), when you change or update the DERIVED NAME in the ADVANCED ELEMENT SETTINGS section of the RG configuration, it messes up the virtual element link (at the element level), resulting in automation links to be broken.
For example, if I change the Derived Name parameter in the RG config from "MCS" to "MCS_NEW", then when running a simple script to read the element name of the "MCS_NEW" virtual element, the script fails to locate the element. And it also fails when using the previous virtual element name.

SAMPLE SCRIPT CODE:

var element = engine.FindElement("MCS_NEW");
engine.GenerateInformation($"Test Run - element data: '{element.ElementName}'");

This issue is reproducible in any system, but to avoid  confusion, our DMS is running on DataMiner (10.6.0.0-17344-CU5)

ERROR SEEING ON IE:

Script Failure (Find Element Test Script): Could not link element to script. Either the element is incorrect, not currently known by Automation engine, or there is a problem with the script. (protocol 1, element 1030, dma 162180)

Please advice on how to recover from this, this is happening right now on our prod DMS.