When trying to copy a Nintex workflow, Sharegate displays one of the following error messages:
The user-defined action 'My user-defined action' is used in the workflow, but it cannot be found at the source. Please re-publish the source workflow and make sure it is valid, then retry the migration.
The user-defined action 'My user-defined action' is used in the workflow, but it cannot be found at the destination. The workflow will not be copied.
|Any error code ending with: -176|
This error occurs when Sharegate tries to copy a Nintex workflow that uses a user-defined action. Since the workflow requires the user-defined action in order to function properly, the workflow cannot be copied unless the user-defined action is also copied. The problem can be caused by two different issues:
- The user-defined action is not found at the source. This usually happens when a workflow is created and it references a user-defined action "A", but "A" is deleted afterwards. The workflow will be left in an invalid state and it will need to be fixed before Sharegate can migrate it. Even if a new user-defined action is created with the name "A", it needs to be reassigned manually to the workflow.
- The user-defined action is not found at the destination. This means that Sharegate was not able to copy it during the migration. If you look at the migration report, you should find an entry for the user-defined action with an error message explaining why it could not be copied.
If the source user-defined action cannot be found, you will need to fix the source workflow to make sure it references a user-defined action that really exists and then re-publish it. Sharegate should then be able to migrate it correctly.
If the user-defined action exists at the source, but Sharegate is unable to copy it, you have two options:
- Look at the migration report to find out what is preventing Sharegate from copying the user-defined action and see if you can fix this error. If you have trouble doing so, do not hesitate to contact us and we will gladly help you find a solution.
- Manually create the user-defined action at the destination. For Sharegate to detect it correctly, it will need to have the same name and be located in the same scope as the source user-defined action. The possible scopes are in the site, in the site collection or in the farm.