We want to be able to execute parallel migrations against the same target folder structure in SharePoint. To prevent dependencies between tasks we have duplicated the folder items within the tasks. However when running in insane mode the creation of a folder within the task that runs at about the same moment might fail because another task already created the folder. In this case we would like to have a retry mechanism implemented that again checks for the presence of the folder and reports the folder item as skipped instead of error. This way we can rely upon thrustworthy reports from the ShareGate migration tool and prevent to have to take care of dependencies between tasks.