@kshitij_jadhav wrote:
is there a workaround to avoid block name change
The workaround is to fix your application's design so that it does not rely on the names of anonymous blocks.
An app or plugin should never rely on the names of anonymous blocks, for the reasons described above, and because an anonymous dynamic block reference can be copied any number of times. When that happens, all of the copies reference the same anonymous dynamic block. When one of the copies is modified, it will reference another new anonymous block having a different name, while the other unmodified copies will still reference the previous anonymous block.
Describe your need for depending on anonymous block names, and perhaps someone can suggest a way to resolve it, but there is no workaround that can prevent an anonymous dynamic block's name from changing when the user modifies its properties.