Nintex Errors
28 articles
- Workflow will be copied, but it will need to be updated to behave as expected
- Cannot guarantee that the dates in workflow action conditions will be accurate with your current Nintex version
- Workflow action cannot be converted from on-premises to Microsoft 365
- The following Nintex workflow actions refer to a custom result source/type which is not supported
- The credentials have not been defined in the External providers configuration, but actions require them
- The parameter of the action is of the type which is not supported in Nintex Workflow on-premises
- This form references functions that are not available at the destination
- The content type/column is generated by Nintex on Microsoft 365 and cannot be migrated
- A Nintex user defined action could not be created at level
- This behavior is not supported with On-Premises Nintex Workflows
- There was an error while adding the required Nintex Live actions on the destination farm
- The destination form was published to Nintex Live with a new URL
- The workflow cannot be copied because it has a Nintex Live action and this service is unavailable at the destination
- The form will not be published to Nintex Live at the destination because this feature is not available on Microsoft 365
- Workflow action/variables cannot be converted from Microsoft 365 to on-premises
- Nintex Workflow on-premises does not support this
- The list item associated to the list is required for this Nintex form and cannot be found at the destination
- This form references Form Variables that are not supported at the destination
- The user-defined action is used in the workflow, but it cannot be found at the source/destination
- The escalation date for the action cannot be converted
- The form is set to allow anonymous access, but anonymous access is disabled on the destination farm
- The form type 'InfoPath' isn't supported for the 'Request Data' user interaction action
- The Nintex workflow seems to be invalid, so it has only been saved at the destination instead of being published
- Workflow action cannot be converted from on-premises to Microsoft 365
- Initializing Nintex Service
- The value will not be preserved in the action because Nintex does not support setting this value when field references are set
- The site/workflow referenced by the workflow action could not be found at the source/destination
- ShareGate Migrate service interfacing with the Nintex Discovery Service is not available