Symptoms
When copying Nintex workflows from Microsoft 365 to SharePoint on-premises, ShareGate Migrate displays one of the following messages:
Multiple workflow associations are linked to the same workflow at the source, but Nintex Workflow on-premises does not support this. The only workflow association that will be available at the destination will be the one that is automatically created when publishing the workflow.
The source workflow association has parameters that differ from the workflow template parameters, but Nintex Workflow on-premises does not support this. The association parameters will be set to the same values as the workflow template's parameters at the destination.
The Nintex workflow contains a contextual action '{0}' that isn't supported at the destination.
Error code
|
Any error code ending with: -190 |
Details
This warning occurs because the source workflow that was built with Nintex Workflow for Microsoft 365 contains parameters that are not available with Nintex Workflow on-premises. The main reason why this could happen is if you had customized the workflow associations in Microsoft 365, since Nintex Workflow on-premises does not allow modifying list and site workflow associations. This means that the association always has the same parameters as the workflow itself and that you cannot have more than one association to the same list or site workflow.
Solution
Since the elements that give you warnings are simply not supported by Nintex Workflow on-premises, it is not possible to get the exact same workflow as you have on Microsoft 365. The best workaround is to make sure that the workflow has the right parameters (start conditions, task list and history list). If you need the workflow to run with different task lists and history lists or in different situations, you can create another workflow with those parameters.