We heavily leverage volume cloning in our environments, and as we are updating some of our Ontap clusters from 9.12.1Px to 9.14.1Px (and some will remain at 9.12), we discovered that now cloned volumes are held in the recovery-queue before deletion meaning that the parent snapshot cannot be deleted after the flexclone has been deleted (held in recovery-queue). if the delete snapshot task fails we need to have the script continue to the next task. how can we accomplish that .
#how to continue to next task when previous task is a failure
spark spire
reef holly