It's not new its always been like that AFAIK. I remember Gilles having a similar issue way back. The alternative is to have lots of variants of the same instrument or increase the admin on the SI side having to check for and remove old UUID's.
I don't think the risk of over writing is there if its managed correctly. There are at least a couple of much easier ways to stop an instrumet being auto-updated that i know of.JackZ wrote: ↑Wed Sep 29, 2021 7:03 am The UUID problem is that this Store requirement needs you to work not on a clone of an existing instrument, but on the original instrument itself in order to keep the existing UUID, and merely change the version number.
If you are improving upon an already present instrument from the Store, be it yours or other’s you are faced with the risk of losing all the changes on your improvements any time when AM updates automatically.
1 - Increase the version number to temporarily 999 and then correct to new version number just before submission. Again AFAIK the auto updater will only update instruments whose version number is earlier than the online version. Ralph or Corjan should be able to confirm or deny this.
2 - Untick the 'Update automatically the instruments and panels' check box in settings.