A Locked Destination Is Unchanged After Snapshot Recall
Diagnosis
Scenario
You recall saved connections that include a locked Destination.
Observed Behavior
The locked Destination retains its current connection rather than the Snapshot's saved connection.
Why This Happens
Snapshot recall leaves locked Destinations unchanged.
Prerequisites
-
Snapshot recall requires Snapshot admin.
-
Lock checks require Control Panel access and access to the affected Destination. Follow the displayed Unlock or Locked (no access to unlock) state and the permissions in Destination Lock States Reference.
-
Confirm whether the Destination must remain protected before attempting another recall.
Resolution
-
Snapshot administrator: Confirm that the Destination is included in the saved scope and inspect the lock indicator on its Connections row. The recall confirmation also states that locked Destinations will not be changed.
-
If the lock must remain, leave the Destination unchanged and record that exception in the operational result. Do not remove the lock merely to make recall complete.
-
If restoring that connection can proceed, follow A Destination Lock Prevents Routing, then recall only the required saved items.
-
If the Destination is not in the saved scope, follow A Snapshot Is Missing Expected Connections instead of changing its lock.
Verify the Result
Confirm that the Destination's connection matches the intended result. A deliberately retained lock should continue to protect its current connection.
Related Information
See Recall Selected Snapshot Items.
If the issue persists after these checks, contact Riedel Customer Success. Include the observations from this page, the Serial Number or Installation ID, the hi version, and a Backup and log export. See Customer Support.