Archive: Nintex for Office 365 Knowledge Articles

ISSUEWhen attempting to run a Update item permissions within a workflow. the following error might occur: Details: ServiceNoResponse The entered and stored passwords do not match.ERROR CODERESOLUTIONVerify " Value" is set to the correct password. Verify the user name is correct by testing it (log into site). Test the current password by logging into site. If you are unable to log in, update the password and try again. With updated password and confirmed User Name, run the workflow again. ADDITIONAL INFORMATIONRELATED LINKS

Issue Nintex Workflow for Office 365 is stuck in progress on an action that needs authorization.One of these actions is Nintex Sign powered by Adobe Sign.   Resolution When the action runs, an email with the below content is sent to the email address selected for the Authorizing user.From: notification@nintexlive.comSubject: Contains phrases "Nintex Live" and "Request authorization".Contents: Contains links to authorize or deny the operation.When the link to provide authorization is clicked the user is prompted to do the following: Log in to the external service. Allow Nintex Live to access the external service. Option to stop receiving future authorization requests for the service.   Additional Information his article applies to all the Nintex Workflow for Office 365 actions that required authorization. Please check the help file of each action for the details regarding the Authorization process.   

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. 

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 using Nintex workflow tasks and using Lazy approval emails can take a long time to send.- As an additional symptom you may receive an “access denied” when approving or denying a task.     ResolutionPlease ensure you have granted Nintex Workflow access to User profile services in the O365 site.Go to your Site -> List ->  Nintex workflow gallery - > *top-right* cog icon -> "Administration Settings" -> Grant Access to Workflow -> Trust the appYou should not need to republish any current workflows.   Additional Informationhttp://help.nintex.com/en-US/o365/o365/O365WorkFlow/Admin/AccessingtheTenantAdministrationSettingsdialogbox.htm Related Linkshttp://help.nintex.com/en-US/o365/o365/O365WorkFlow/Admin/AccessingtheTenantAdministrationSettingsdialogbox.htm 

ISSUEWhen a Nintex Form uses the Attachment Control, and a user goes to add an attachment, the control will not load as expected. RESOLUTIONCheck to see if there are any rules on this form.  If so check if there are duplicated rules (same formulas).  This issue is caused by inserted references being copy/pasted to the formula instead of being properly inserted by double clicking the desired references on the sidebar. Check to see if there are any calculated value control on this form. If so check if the formula of the calculated value controls are written correctly.  This issue is caused when assigned a formula to one of the item properties with Equal sign (==). Equal sign is only use if there is comparison between 2 values.  Delete the control and re-add it. ADDITIONAL INFORMATIONWhen references are copy/pasted instead of properly inserted, the unique ID for the control is not properly stored in the XML and thus may cause adverse effects.  In this instance, it broke the Attachment con

ISSUEWhen creating a new workflow in Nintex Workflow for Office 365, a "For development use only" message appears in the background.ERROR CODERESOLUTIONThis is by design. Workflows will be marked as 'For development use only' until the workflow has been assigned to production on publishing. For more information, see How to Designate a Production or Development Workflow in O365.ADDITIONAL INFORMATIONRELATED LINKS

IssueAn Office 365 workflow becomes suspended and the only error message in the workflow history is 'Forbidden.'  ResolutionGrant access to write to the Workflow History list for the SharePoint site to the user account running the workflow. This will allow the workflow to display the true error which can then be used to resolve the underlying issue. Additional InformationWhen an O365 subscription has less than 30 days to the end of the subscription a message is written to the Workflow History list advising of this.This message is written using the permissions of the workflow Initiator.  If the workflow has an action set as the first action configured to run with elevated permissions the message will still be written with the Initiators account.  If the Initiator does not have access to the Workflow History list in this scenario the workflow will suspend with an access error.

IssueWhen using a Send an Email action in a workflow created in Nintex Workflow for Office 365, 1.0.4.0, and changing the formatting of any “inserted reference” item, it will create many empty SPAN tags in the HTML. Resolution  Additional InformationThis is a known issue that is currently under investigation. 

ISSUEWhen attempting to email a shared mailbox via an Office 365 Nintex Workflow the 'Send Email' action is unable to resolve the Shared Mailbox account.ERROR CODERESOLUTIONCheck to see if the email account can receive emails from a different source e.g. Gmail. If the shared mailbox can receive email, then utilize the 'External Email & Attachment' option. If the Shared Mailbox was setup and configured as an Office 365 Shared Mailbox then emails should be received with both options.ADDITIONAL INFORMATIONRELATED LINKS

 ISSUEWorkflow suspends when attempting to send an email to SharePoint group. ERROR CODEDetails of last request: HTTP Forbidden to {SiteURL}/_api/sp.utilities.utility.SendEmail Access Denied. You do not have permission to perform this action or access this resource. RESOLUTIONIn the site from which the workflow is running, open the Site Settings. Under Users and Permissions, navigate to People and groups. From the groups on the left-hand side of the window, select the SharePoint group where the email is being sent. Select Settings at the top of the group list, and then select Group Settings from the drop-down menu. Change Who can view the membership of the group? from Group Members to Everyone. Click OK. Run the workflow again. ADDITIONAL INFORMATIONIf the user account initiating the workflow instance is not a member of a SharePoint group, the workflow will not be able to view the group membership and resolve recipients. Any workflow action referring to a SharePoint group in which the

IssueAfter configuring the Send Email action, when selecting save the action errors with:Oops! Something went wrong. Email - dispose : TypeError: Object expected Error CodeOops! Something went wrong. Email - dispose : TypeError: Object expected ResolutionUse a browser other than Edge for workflow design, as it is not supported by Nintex for Office 365.  Related LinksNintex Workflow Supported Browsers 

IssueWhen using an action in Nintex Workflow for Office 365 that utilize Connection Manager, this error might occur:Identity Client Runtime library (IDCRL) encounterdd an error while talking the partner STS ResolutionReset the password of the account credentials of the Connection Manager.  Additional InformationThe password of the account that is used on Connection Manager has expired.This happened even for the account that has been set to password never expires.  

IssueWhen using Office 365 update item permissions action with connection manager, this error might occur:Unable to reach destination server.  ResolutionThis is a known issue and has been resolved in the latest version of Office 365 update item permissions action. User required to drag and drop a new action into a Nintex Workflow Designer for Office 365 to get the latest version of the action.   

QuestionHow often do O365 actions retry if they fail to connect to the O365 tenant. AnswerEach query execution has a timeout of 1.5 minutes. The default timeout of the SharePoint SDK (CSOM) is what is usedAll Office 365 actions have the same retry behavior. Additional InformationTo add functionality to the the O365 workflow engine Nintex's Office 365 actions call outside of the tenant to Nintex Infrastructure.  The Nintex infrastructure then logs back into the tenant to perform the required activity.  Sometimes there can be issues with connecting to the tenant due to a range of issues between Microsoft, Nintex and the Internet.  As this is the case Nintex has retry functionality built in so that the workflow does not immediately suspend.  

IssueWhen responding to a Lazy Approval task notification, the following error might occur:Your response to this task was not able to be interpreted. The following phrase is invalid. ResolutionOnly reply with the valid phrase on a line by itself at the top of the email. 

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 

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.