VPLEX mobility clarification

We had a sick array that worst case scenario might have been reboot and not come back up.  We used VPLEX data mobility to move critical production data to another array.  The original storage-volumes/extents/devices were left in place so we could migrate back if the sick array recovered.  It appears to be impossible to use the original storage volumes.  My first attempt to create the mobility jobs to reverse the process failed to create the jobs ' application-consistent ' error.  I couldn't update the attribute until I deleted the device and extent.  I submitted the data mobility again this time with a critical error ' out of date '.  Do I need to tear down all the original volumes, un-claim them, remove them from the VPLEX array storage group, forget them in VPLEX then delete/recreate the volumes from the array then bring them back into VPLEX to use for data mobility?