Archive: Nintex for Office 365 Knowledge Articles

IssueSharePoint Online workflows are stuck in a 'Started' state, and the blue information bubble states the following:"Access denied. You do not have permission to perform this action or access this resource" Error CodeResolutionGrant workflow initiators 'Contribute' permissions to the Workflow History list. The Workflow History list can be accessed at the following URL: https://[TenantName].sharepoint.com/sites/[SiteName]/Lists/Workflow%20History/AllItems.aspx Additional InformationGuidance from Microsoft on managing list permissions can be found in the Related Links section below. Contribute permissions are needed for the workflow initiator to log workflow history entries to the Workflow History list. When a subscription is within 30 days of expiring, a workflow history entry stating "Nintex Workflow for Office 365 subscription is due to expire" is logged in every workflow instance until your subscription is renewed, and there is no way to disable this message. Related LinksCustomize

ISSUEWhen opening Nintex Forms, the following error occurs:An error occured while parsing EntityName. Line 123, position 29598.ERROR CODERESOLUTIONEnsure the form is complete.  Save the list as a list template.  Create a new list with the template.  Add the form to the new list.ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen trying to publish a workflow, you may receive this error."Error publishing workflow. Unable to cast object of type"... 'System.Double' to type 'System.String', or '[Microsoft.Activities.DynamicValue]' to type '[System.String]'.This is usually caused by a Set Variable action or a Math Operation where the data types do not match. The System.Double to type System.String may give you a clue where the issue lies within your workflow. ResolutionReview the workflow in question for any Set Variable actions or Math Operation actions. You will need to verify there are no mismatched data types, i.e. Integer to String, in your actions. 

IssueWhen responding a Task via Lazy Approval using a button in Actionable Message in Outlook Online with Edge browser, this error might occurs: The action could not be completed ResolutionUse another browser than Edge. We support IE9 and above, however we recommend using IE10 and above. We also support the latest versions of Firefox and Chrome. Additional InformationEdge browser does not supported yet in Nintex Workflow for Office 365. Related LinksNintex Workflow Supported Browser 

TopicThis article is applicable to the new Office 365 Tenants that were created after August 25, 2020.   When trying to open Nintex Workflow for Office 365 Designer this error may occur:"Oops... something went wrong. Please visit status.nintex.com for the latest status or contact your system administrator to check the health of your Office 365 tenancy"  InstructionsResolution 1:Run this script in SharePoint Online Powershell:Set-SPOTenant -DisableCustomAppAuthentication $false Reference: https://docs.microsoft.com/en-us/sharepoint/troubleshoot/workflows/nintex-workflow-fails-to-start Resolution 2:Grant the "Nintex Workflow for Office 365" App Trust. This required Global Administrator permission.  Steps:Get the Nintex Workflow for Office 365 App Identifier Navigate to the Root Site that has Nintex Workflow for Office 365 is installed. Then navigate Site Setting > Site App Permission. On this page, the app permissions will be displayed for all apps on your site. Copy the client sect

IssueRunning workflow will automatically terminate with the following error: The workflow instance exceeded the CPU usage limit of throttle of 00:00:01.2000000 and could not be unloaded because it was not persistable. Error Code"The workflow instance exceeded the CPU usage limit of throttle of 00:00:01.2000000 and could not be unloaded because it was not persistable." ResolutionResume the suspended workflow instance by clicking Resume for the workflow or by using the SharePoint Workflow Client Object Model after 24 hours have passed. This must occur before the workflow is terminated. Redesign the workflow to follow Microsoft best practices to handle throttling. For more information, see SharePoint 2013 workflow throttling and performance in SharePoint Online and Project Online.    Related Linkshttps://support.microsoft.com/en-us/help/3076399/sharepoint-2013-workflow-throttling-and-performance-in-sharepoint-onli 

IssueWhen attempting to authorize with Nintex Sign, you receive the 'Oops something went wrong" error.In the Nintex Sign Authorization email, you see this URL for the link to authorize. ResolutionReview the Mimecast encoding/decoding settings. There should be a setting to adjust for specific URLs. Once this is updated, you will be able to access the correct URL. 

Issue When update a value to an a list column, you will get get the following error "A text field contains invalid data”   Resolution Your list column may be Single Line Text. When changed to Multiple Line Text the workflow will resume and complete as normal.  

IssueWhen using an Office 365 Upload File action to upload a file to the list that has a special character as the list name (i.e : (Nintex) List Sample), the following error may occur: The list '<List Name>' does not exist in web site '<Site URL>' ResolutionThe issue has been fixed on the latest version of Nintex Workflow for Office 365 Apps that is being released by the end of August 2018. Make sure that the site has the latest version of Nintex Apps.     

ISSUEWhen running a workflow that is configured to send an email, the workflow suspends with the following error: RequestorId: 6fdb72dd-529e-e60f-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 400 {"error":{"code":"-2130242040, Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"The e-mail message cannot be sent. Make sure the e-mail has a valid recipient."}}}ERROR CODERequestorId: 6fdb72dd-529e-e60f-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 400 {"error":{"code":"-2130242040, Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"The e-mail message cannot be sent. Make sure the e-mail has a valid recipient."}}}RESOLUTIONWhen trying to send to an email that is not associated with an account within SharePoint Online, ensure that t

IssueWhen opening the Nintex Forms Designer there is no option to select New Responsive Forms. ResolutionNavigate to site contents in classic mode and look for the Nintex Forms application.If there is an update available perform the update and test.If the issue persists, remove the Nintex Forms application from the site and then add it back again. 

IssueWhen assigning workflow tasks no tasks are assigned.  This issue will also occur with SharePoint Designer workflows as well as Nintex Workflows. ResolutionNavigate to Site Settings > Site Permissions > Edit User Permissions and uncheck Limited Access. Related Linkshttps://community.nintex.com/message/81553-re-tasks-not-being-assigned?commentID=81553&et=watches.email.thread#comment-81553 

IssueWhen uploading a document to a document library in SharePoint Online that has a Nintex Form published, Internet Explorer presents a window that states "This content cannot be displayed in a frame". Resolution In Internet Explorer, please navigate to Settings (Cog in top right) > Internet Options > Security > Trusted Sites > Sites and add the following sites:*.office.com*.microsoftonline.comYou may need to close and reopen Internet Explorer for this to take affect. Error Code"This content cannot be displayed in a frame" Additional InformationThis appears to only occur when there is a SharePoint Column that is 'Required'. 

ISSUEWhen using a customized Nintex Form within Office 365, the form might have an initial load time of 15 seconds or more.ERROR CODERESOLUTIONAs all custom forms are unique, here are some of the most common fixes for long load times with Office 365 Forms:Reduce the number of controls. Make sure that all of the controls that are on the form are needed, and if there are any that were there for testing purposes, remove them. Reduce the number of rules. Review the rules that are being used on the form, and if there are several rules that accomplish the same outcome, reduce the duplicate rules and apply the single rule to multiple controls on the form. Break the form into multiple forms with redirects. If the form has logical break points, separate it into multiple forms, and use redirects to move the end user to the next stage of the form.ADDITIONAL INFORMATIONRELATED LINKS

ISSUEWhen opening a Form in Designer, an error similar to the following might occur:'[]', Hexadecimal value 0x13, is an invalid character. Line 124, position 28653.ERROR CODERESOLUTIONOPTION 1Re-create the affected list from the template (save list as a template).  Rebuild or import the backup Form file to the new listOPTION 2Find where the Form is located in the Office 365 environment and delete the Form by referring this article here.  Rebuild or import the Nintex Form, from a backup file.ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen using "Office 365 upload file" action and the file name contains a special character such as {} ~, the following error may occur: Some parameters failed the validation check. - [InputDestinationFileName] : The file name is invalid. ResolutionThis issue has been fixed on the latest version of Nintex Workflow for Office 365.  

IssueWhen trying to assign a task to a user, the workflow fails with the error: 'Failed To Resolve User' ResolutionVerify that the user is recognized within the SharePoint Online User Profile Service, and that they have a valid email associated with their profile. Error CodeFailed To Resolve User 

IssueWhen Submitting a Nintex Form, the following error may occur: hexadecimal value 0x0B, is an invalid character ResolutionMake sure to type all the values for the Form. If the user requires to copy and paste the values from another source then please do paste the values into Notepad. After that, copy the values from the Notepad into the Nintex Form. Additional InformationThis error is because the submitted value contains a special or unknown character such as "[ ]" when a content has been copied from another source such as Words, PowerPoint, Website content, etc.  

IssueWhen connecting to a database or running an Execute SQL action, the following error occurs:HTTP InternalServerError to https://<domain>.sharepoint.com/<GUIDs>Correlation Id: <GUID>Instance Id: <GUID>Invalid text value.A text field contains invalid data. Please check the value and try again. ResolutionEnsure the Connection String is properly formatted, contains no typographical errors, and is not pointing to a server with a private IP address. Error CodeHTTP InternalServerError to https://YOURDOMAIN.sharepoint.com/ Correlation Id: Instance Id: Invalid text value. A text field contains invalid data. Please check the value and try again. Related LinksConnection String TesterPrivate IPv4 address spaces Wikipedia article 

TopicWhen using "Start Workflow" action in the Nintex Workflow for Office 365 to start a workflow in a SharePoint List that has more than 5000 items, the following error may occur: The attempted operation is prohibited because it exceeds the list view threshold enforced by the administrator. InstructionsModify the "Start Workflow" action configuration of the field "Item ID or GUID" to use the Item ID instead of GUID. Additional Information  Related Links https://help.nintex.com/en-US/office365/Designer/Actions/StartWorkflow.htm 

IssueThe O365 Set Approval Status action is used to Set the approval status for items in a list or document library on SharePoint Online.When using this action on items located in a Folder or a Document set the error : "Unable to find list item to update" can occur. Error Code"Unable to find list item to update" ResolutionIn the Items to update section of the action configuration make sure the "Search Folders" check box is ticked.

IssueWhen opening Nintex Forms or Forms designer on a SharePoint online site collection that has a Japanese subsite, instead of the regular “Working on it” message, users are seeing Japanese characters. ResolutionManually update the Nintex Forms App to version 1.2.4.1Note:If customers are running 1.2.4.0 App with unsupported language site with the new forms services then to resolve the issue, they need to remove the 1.2.4.0 and re-Add 1.2.4.1 app. If updating from version 1.2.3.x or earlier to 1.2.4.1 the issue should be resolved without the need to remove and add the App. Error CodeThe loading text should be in English, unless you're in a Japanese environment. 

IssueWhen using Office 365 Create List Item or Document Set action for a Document Library with Document Set configured  and the Library has been renamed, this error might occurs:Folder for the new list item does not exist or the current user lacks permissions to the folder.  ResolutionThe issue has been identified and has been fixed on the latest Apps of Nintex Workflow for Office 365. Make sure the Nintex Apps has been updated into latest version. Manually Update O365 Apps. Drag and drop a new "Office 365 Create List Item or Document Set" to the workflow designer.  

IssueWorkflows within SharePoint Online will randomly suspend or terminate, and within the Instance Information panel (accessed through the blue 'i' on the Workflow Status page) is the message: 'HTTP status code 429' ResolutionReduce the number of requests that are being made into the SharePoint Online environment by the workflow Review Handling Workflow Throttling  Error CodeHTTP status code 429 Additional InformationMicrosoft's documentation on avoiding workflow throttling within SharePoint Online 

IssueNintex O365 Workflow fails to complete once permission has been removed for current item even though the workflow is using Action Step. ResolutionThe solution to this design is to create a new workflow on the same list/library with Start Workflow Action. This action is calling the second workflow which is running under the credentials supplied in the Start Workflow action. This way the second workflow can “see” the item after the permission removal.