Archive: Nintex for Office 365 Knowledge Articles

IssueWhen using "Send an Email" action with a user in Office 365, the following error is occurred : The message could not be delivered to one or more recipients ResolutionMake sure that the email is for a valid and active user.  Terminate and re-run the workflow. If the issue still persist, contact Nintex Support with the details of the email address, this will expedite the discovery of logs.  Additional InformationThe issue is intermittent and only occurs for periods of time.  The root cause is the email address has been soft blacklist by Nintex Mail Service, due to it previously attempting to send an email with an attachment that exceeded the size limit.  

IssueWhen opening the Nintex Workflow designer within Office 365,  there is a red bar displayingError Connecting to the Workflow Manager: undefinedOr:Error Connecting to the Workflow Manager ResolutionOption 1 Add the following to the trusted sites for the browser: *.nintex.com *.sharepoint.com  Deactivate and Reactivate the "Workflow can use app permissions" site feature.  Ensure the user account has the appropriate permissions to access the designer.Option 2Contact Microsoft SharePoint Support to resolve the underlying connection error between the site and SharePoint Workflow Manager. Additional InformationIf the above doesn't work then please try the following steps in the link below:https://community.nintex.com/t5/Technical-Issues/Enable-SharePoint-2013-workflows-in-Sharepoint-Online-Office-365/ta-p/86006 

IssueWhen using Office 365 update Item Permission action, it give an output of the List item URL that can not be use afterward. The URL format return by the List item URL as below: ["https://site_url/Lists/list_name/DispForm.aspx?id=2"]   ResolutionConvert the List item URL that has a Collection data type into single text by utilize action "Get Item From Collection".  Additional InformationThe details of "Get Item From Collection" can be found here. Related LinksHelp file "Get Item From Collection" 

ISSUEWhen using a state machine action in a workflow, the workflow processes actions after the change state action, instead of changing states.ERROR CODERESOLUTIONReorganize the workflow so that change state actions occur as the last actions in the state machine.ADDITIONAL INFORMATIONThis is expected behavior for a state machine. The state machine will continue to the end of its logical loop prior to trying to change states. At the end of the loop it evaluates to which state it should change. If there are multiple places with change states it will change to whatever state it was last set.RELATED LINKS

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

IssueWhen configuring the Document Generation action, the configuration indicates the document quota has been exceeded, even when no documents have been created. ResolutionContact Sales@Nintex.com. Have Sales verify that the 'Nintex for Office 365' asset and 'Nintex Document Generation' asset are active. If both assets are active, confirm that both assets are on the same contract. Even if both assets are created and live, if they're on separate Salesforce contracts, Document Generation for Office 365 will not work.   Additional InformationThis is caused by a mismatch in the licensing with the associated customer account.Looking at the JSON call that is made when the action configuration loads, you will see the following inside of developer tools: {"Total":0,"Used":0,"IsTrial":false,"SubscriptionStartDate":"0001-01-01T00:00:00","SubscriptionEndDate":"0001-01-01T00:00:00","OverUsage":0,"QuotaOverageAllowance":0,"ErrorType":400,"IsSuccess":false,"ErrorPayload":null,"Info":null,"Subscripti

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 

IssueWhen building a conditional rule with a numeric value,  the rule does not work. For example a form with a rule such as: ControlName >= '25,000' can be submitted even when ControlName is greater than 25,000. ResolutionForm rules with number values should not include commas. Update the rule to just use integers. For example, ControlName >= '25000' 

ISSUEWhen submit Task using Nintex Task Form, the following error might occur: Index was outside the bounds of the arrayERROR CODERESOLUTIONReview the Form to make sure all the fields are configured properly and that there is an Approve / Reject button in the Task Form.ADDITIONAL INFORMATIONRELATED LINKS

ISSUEWhile trying to publish a workflow within Office 365, the publish fails with the error:Error publishing workflow. Microsoft.Workflow.Client.WorkflowManagementExcept. A response was returned that did not come from the Workflow Manager. Status code = 503: Service UnavailableERROR CODERESOLUTIONContact Microsoft SharePoint Online support to troubleshoot and resolve issues or failures with the underlying Workflow Manager system in SharePoint Online.ADDITIONAL INFORMATIONRELATED LINKS

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 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 using Nintex Workflow for Office 365 Document Generation action, some of the items properties that have been tagged in the Document Template do not generate a value on the document generated.  ResolutionBelow are some Verify the item property tag on the document template and make sure that the tagger has a space with another word on the template. Example: (1)<<ItemProperty_Title>> ==> This will not work because there is no space between character  ) and <<. The valid tagged is:(1) <<ItemProperty_Title>> ==> Add one space between (1) and <<ItemProperty_Title>> 

IssueTask Reminders are not being sent out. ResolutionResolution 1:In O365, Task Reminders are sent after the task is overdue. This is determined by the Due Date field in the task settings. Once the task is overdue, the reminder emails will start to process. If you want to escalate or auto complete the task after all reminders have been sent out, you can set this in the 'Escalate and auto-complete options'.If these options aren't set the Task will be patiently waiting to be updated.This information is also listed in the Help Documentation for the Assign a Task action.Resolution 2:When the Wait for task completion checkbox is not selected, the action will not send escalation or reminder emails. Related Linkshttps://help.nintex.com/en-US/O365/Default.htm#cshid=1011 

IssueWhen using LazyApproval with Nintex for Office 365, if the task assignee has an 'out of office' response, the LazyApproval system sends a second email saying that their response was not valid.  ResolutionThis is currently expected behavior within Office 365, as LazyApproval within Office 365 currently does not support LazyApproval. There is a feature request for this functionality which can be found here. 

IssueThe Shrink and Expand button are disabled in the New Responsive Designer.  ResolutionThe Shrink and Expand buttons are only enabled if there is more than 1 control in the same row. The buttons are disabled if only 1 control in the same row.  

IssueWhen accessing task form as a user who did not initiate the workflow, the error "Item does not exist. It may have been deleted by another user." pops up instead of loading the task form. ResolutionNavigate to List Settings > Advanced Settings on the affected list. Under Item-level Permissions, make sure "Read all items" and "Create and edit all items" are selected.  Error Code"Item does not exist. It may have been deleted by another user." Additional InformationNintex task forms check item-level permissions when allowing access to the task form.  If access isn't set to all items, then only the workflow initiator will have access and everyone else will receive the error message. 

IssueNumbers entered in Nintex form are being registered with comer in SharePoint when the Nintex form control is connected to a SharePoint column with the “Number” data typeThis is for all platforms of Nintex Form and SharePoint  ResolutionThis is a know issue in SharePoint, this is not a Nintex issue.There are workarounds1, Use a text column and not an number column data type2, Create a calculated column and use the formula = TEXT([Column Name], "0") 

ISSUEWhen opening the Nintex Form for Office 365, the following error may occur: The given key was not present in the dictionary. ERROR CODERESOLUTIONVerify that the SharePoint Online List / Library setting for the Lookup data type column has a valid reference to the other List.ADDITIONAL INFORMATIONWhen creating a SharePoint List / Library from a list template, the reference for the Lookup column might be lost. RELATED LINKS

IssueAttempting to edit a Nintex form causes an Nintex error page to appear with the below error.Error message:#ERR  ResolutionNavigate to List Settings in the list ribbon and edit and save the list lookup columns. The Nintex form has lost connection to a list lookup field and saving the field settings will restore the connection. Error CodeFront End: Application_Error => Microsoft.SharePoint.Client.ServerException: #ERR at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream) at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse() at Nintex.Forms.SharePoint.BatchedContext.ExecuteQuery() at Nintex.Forms.SharePoint.SharePointContexPage.InitializeCulture() at ASP.pages_formspart_aspx.FrameworkInitialize() at System.Web.UI.Page.d__10.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSucces

IssueNintex O365 Workflow does not start automatically ResolutionThere are few possible solutions to this issue:- ensure that group members are allowed to see each other - ensure members and group are added to the Nintex History list with Contribute permission- ensure App permission is activated at the root site and the sub-site level  

TopicWhen trying to start a Component Workflow from another Component Workflow which started from the List Workflow, the following error may occur: "Could not start child workflow" InstructionsThe maximum depth limit when calling component workflows is set to one. The parent-child workflow depth cannot exceed one.  Additional Information For example, consider the following scenarios with different depths:Scenario 1: A List workflow is designed to start Component workflow 1 and Component workflow 1 starts Component workflow 2. This workflow will fail in this scenario as the depth exceeds the limit as shown below: List workflow (depth 0) Component workflow 1 (depth 1) Component workflow 2 (depth 2) Scenario 2: Component workflow 1 that starts Component workflow 2 is added to a workflow. The workflow is successful because the depth does not exceed the limit value as shown below: Component workflow 1 (depth 0) Component workflow 2 (depth 1)  Related Linkshttps://help.nintex.com/en-US/o

ISSUEWhen opening Nintex Forms, the following error occurs:Index was outside the bounds of the arrayERROR CODERESOLUTIONReview all site column names and remove any special characters, for example: / : * ? " # % < > |, two consecutive periods (..), or special characters such as a tab.ADDITIONAL INFORMATIONRELATED LINKS