Archive: Nintex for Office 365 Knowledge Articles

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

IssueWhen using the action 'Get an Item from a Dictionary' inside the 'Loop N Times', to get each item within a dictionary variable, within in Nintex Workflow for Office 365. The workflow only returns the first value of the dictionary and ignores the remaining items.  ResolutionWhen referencing items in an array, use "(0)" for the first item, "(1)" for the second item, and so on.  For the 'Item name or path' field, of the workflow action 'Get an Item from a Dictionary', ensure that this field is configured with an 'index' variable used in the above point.  The index variable has to increment (+ 1) during each "for each loop" iteration Related LinksHelp file : Get an Item from a Dictionary  

IssueWhen using Google Chrome version 72 (was released on the 29th of January 2019), the Nintex Task Form cannot be modified in the Responsive Form designer. As well as: To Add a new control onto Nintex Task Form Designer.  Drag and drop controls in the Nintex Task Form Designer.  ResolutionClose all instances of the Chrome browser.  Navigate to the directory where the Chrome browser has been installed. This is either C:Program Files (x86)GoogleChromeApplication or C:Program FilesGoogleChromeApplication. . Then Run the following command from command prompt:  - chrome.exe --disable-features=VizHitTestSurfaceLayer,VizHitTestDrawQuad,VizDisplayCompositor Additional InformationThe Chromium team has confirmed this issue on Google Chrome version 72 and they are working towards a permanent fix for the next released of Google Chrome. 

IssueNintex 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. ResolutionWhen 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 Informationhis 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.  

Issue Office 365 Nintex workflows are triggering multiple instances.   Resolution Open the Nintex workflow causing issues in the Nintex Workflow designer. Navigate to the workflow settings in the designer ribbon and check the workflow start conditions. It possible the workflow is configured to start when a item is updated or when a specific condition is met. The workflow is most likely meeting multiple start conditions, causing the workflow to trigger more then once. Example: The workflow is configured to start when a item is created or modified. The workflow starts and the first action performs an update to the current item. The update causes the workflow to start again based on the workflow start conditions. The workflow start conditions need to be adjusted or the workflow design changed.  

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 completing a Nintex Task Form associated with a Nintex Workflow, SharePoint displays the error message "Unexpected error occurred."ERROR CODEFrom the GUI: Unexpected error occurred. If the problem persists, contact your support team with the following information: Correlation ID: xxxxxx Tenant ID: xxxxxx Time (UTC): YYYY-MM-DD HH:MM:SS From Logs: - Task Outcome Control 'outcomeCtrl' is not found in form - Nintex.Forms.SharePoint.Exceptions.UserException: Error in task. Input string was not in a correct format. - Exception caught by error page. => Nintex.Forms.SharePoint.Exceptions.UserException: Error in task. Input string was not in a correct format. - Application_Error => System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown.RESOLUTIONMake sure the task form has the "Task Outcome" control present or SharePoint will throw an error message when closing the form.ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen a document is uploaded in a document library with Nintex forms, the browse button is missing from the managed metadata field.  ResolutionThe Manage Metadata control does not support browsing MMD terms when the item is opened in the pop up dialog mode. Workaround On document upload in a document library that has Nintex form published pop up dialog for new form is missing the browse feature for MMD control as it is not supported. Instead use the free text search functionality by typing the required term in the MMD field. Alternatively use the "Modern SharePoint UI" as "Modern SharePoint UI" does not open the new form in a dialog.  

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. 

IssueWhen replying to a Lazy Approval email with a valid outcome the email does not seem to be received by the O365 tenant and the Task remains in the status of Not Started. ResolutionThere are many reasons why this issue can occur but these are the basic things to check.1. Navigate to the Nintex status page and check for any incidents concerning Lazy Approval.2. Make sure that the Email infrastructure is not changing the domain for outgoing emails as the task can only be completed if a reply is received from the email address that it was sent to.3. Make sure that the Email infrastructure is not altering the subject line of the email and altering the Lazy Approval token. Related LinksNintex Status Page : Nintex Services 

IssueWhen try to save or publish the workflow, this error might occurs:ButtonPanel - handleXamlBuildError : SyntaxError: Invalid characterAn error occurred that could be due to size of the workflow. Try reducing the size of your workflow. For example, reduce the size of task forms or split up the workflow. ResolutionSplit the single workflow into multiple workflows.  Additional InformationWhile there can be many causes for these errors, one of them can be when you have too many tasks in parallel in a single workflow. A large workflow has more tasks and more updates in the single workflow, so more chance of causing a lock. Also if a lock does occur, a larger workflow can make it difficult to determine the point at which the lock happened while a smaller workflow will always be easier to diagnose. Related LinksSplitting large or complex workflowsExample: Splitting up a large workflowWorkflow sizing guidelinesDetermine the size of a workflow 

IssueWhen trying to publish the Form, this error might occurs:Failed to Publish. ResolutionNavigate to Nintex Form hidden library. https://SiteURL/NintexFormXML/ Verify that all the files here has been checked in. If there are files has been checked out, then it needs to be check in.  Resolve the error during the check in (if any). Possible error during the check in:Sorry, something went wrongYou must fill out all required properties before checking in this document. Those error above indicating there some required additional field that does not created by Nintex has been added to the Nintex Form hidden library. As resolution, go to the Library setting and set to No for the required fields.  

IssueWhen using the Office 365 workflow actions, the workflow instance suspends with the error: 'Unable obtain security token, authentication failed.' ResolutionVerify that the account being used does not have Multi-Factor Authentication (MFA) enabled, as MFA is not currently supported by Nintex for Office 365 Verify that the action works with an @domain.onmicrosoft.com account vs. an @domain.com account. Success with an @domain.onmicrosft.com account vs a domain account will indicate an issue with ADFS. The Microsoft Remote Connectivity Analyzer can be used to investigate ADFS issues further.  Error CodeUnable obtain security token, authentication failed. Additional InformationSteps for testing with Microsoft Remote Connectivity Analyzer: Microsoft Remote Connectivity Analyzer Select Office 365 tab Under Office 365 General Tests select 'Office 365 Single Sign-On Test' Select 'Next' Fill in domain user credentials and the verification captcha Select 'Perform Test' Review results for A

IssueWhen trying to open a Nintex Form Designer for Office 365, the form is not opened and the following errors may occurs:The site is undefined An embedded page at formso365.nintex.com - An error occurred during an Ajax call. No error but the form is not opening, only showing spinning icon. ResolutionFind the ID of the form that corrupted by following this article here. And take a note of the Form ID.  Navigate to https://SiteURL/NintexFormXml/Forms/AllItems.aspx Identify the Form file here based on the Form ID from step 1.  Click the ellipses of the item and select version history. Restore the previous version of the form (Note: you may need to roll back further versions if multiple versions of the XML are corrupt). Navigate back to the list where the issue occurred. Open the forms designer to ensure the issue is resolved. 

IssueWhen an Office 365 workflow runs after a task becomes overdue, the following error might occur:Workflow was unable to authenticate this request. Detail: Token could not be retrieved; retries exceeded the limit Error CodeError “Workflow was unable to authenticate this request. Detail: Token could not be retrieved; retries exceeded the limit” ResolutionEnsure that the task escalates to a valid user or group account:Open the affected workflow in Nintex Workflow Designer for Office 365. Double-click the Task action that caused the workflow suspension.  Navigate to "Escalate and auto-complete options". Check the value from the field "Escalate to". Ensure this User or Group exists within the SharePoint Online environment.Go to Site Setting > People and Group. Find if the user or group from this page. If the User or Group does not exist, either create this account or update the Task action to escalate to a valid account.?

IssueWhen trying to use any of the the Nintex Office 365 REST API functionalities, the API request will fail without having the tenants API key. ResolutionUse the API Key Request Form to obtain the necessary Office 365 tenant API key.  

IssueWhen using Quest's Mextalogix Essentials for Office 365, Nintex workflows fail to migrate with an "unauthorized" error. ResolutionEnsure that you have whitelisted https://nintex.onmetalogix.com. You can check the availability of this services URL by visiting https://nintex.onmetalogix.com/nintex/version, and you will see a result similar to the screenshot below:  

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 trying to open a workflow in Nintex Workflow for Office 365 that contains 'Run Component Workflow' action, the following error may occur: Error opening a workflow. Object reference not set to an instance of an object ResolutionThe issue has been fixed on the latest version of Nintex Workflow for Office 365 Apps that is being released by the end of July 2018. Make sure that the site has the latest version of Nintex Apps. 

ISSUEWhen running a workflow that uses the "Start workflow" action to start another List workflow, the selected workflow does not start even though the master workflow does not return any error. ERROR CODERESOLUTIONConfigure "Workflow type" value in "Start workflow" action with "List Workflow". ADDITIONAL INFORMATIONRELATED LINKSStart workflow

IssueWhen trying to access Nintex Forms or Workflow designer in Nintex for Office 365, the following error might occur.This page can't be displayedTurn on TLS 1.0. TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to <Nintex cloud host URL> again.If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such an RC4, which is not considered secure. Please contact your site administrator. Error CodeThis page can't be displayedTurn on TLS 1.0. TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://xxx-xxx-xxx.nintexo365.net again.If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such an RC4, which is not considered secure. Please contact your site administrator. ResolutionContact your Network Administrator to white-list the Nintex cloud host URL mentioned in the error message. Additional InformationThis is caused by a Network access restriction (like a firewall or a

IssueEven though reminders have been set for Start a Task Process action, the notifications are not being receive. ResolutionTo receive task reminders with Nintex Workflow for Office 365, you need to set the Due Date within the action configuration. If the Due Date is blank the reminders will not be sent as the workflow wouldn't know when the Task is due is actually due. Additional InformationYou can read further information and the Task action configuration options in the the help file below.Start a Task Process 

IssueWhen running Nintex Workflow for Office 365, the following message appears in the Workflow status history page:The list '{Workflow Context:List Name}' does not exist in the web site ResolutionThe error is shown when the 'List name' field has either been entered in manually or copied and pasted from a similar account. To resolve the issue, you will need to do the following:1. Open the Workflow Designer2. Open the Office 365 Live action3. Clear the existing field for 'List name'4. Place cursor in the 'List name' field5. Expand 'Workflow Context' section on the right6. Click on 'List Name' to add this information to the 'List name' field 

IssueWhen using Nintex Forms Choice Control and creating rules that reference the choices, the rules do not properly respond when editing the form. ResolutionEnsure that the choice reference in the associated rule is the exact same string as the choice options listed in the control.  Additional InformationChoices: Sales, Marketing, IT, Support- Notice that there is a space after every comma, thus the rule needs to be written with the white space.Condition != 'Sales'Condition != ' Marketing'Condition != ' IT'Condition != ' Support'Choices: Sales,Marketing,IT,Support-Alternatively this is how rules should look with no white space in the choice control.Condition != 'Sales'Condition != 'Marketing'Condition != 'IT'Condition != 'Support' 

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