Okay, this is an interesting one.
I agree it’s a pain point; it “makes sense” why it behaves this way. If I copy and paste (keeping the original) things work fine, and there are new mutator zones that aren’t being used.
If I cut and then paste in order to move it, because I have cut the original, the new instance is technically different, so the editable reference on the device is still pointing to the old, now deleted mutator zone.
I can understand why it’s this way, because there’s nothing stopping a user from pasting many new instances from that same cut. Though it’d be nice if it could better handle something like this as it’s a pain working with live edit.
There might be programming considerations I’m not thinking of for why it must be the way it is, but I’ll pass this to the engineering team to discuss.
Thanks for the report.
Allan