Archive: Nintex for Office 365 Knowledge Articles

IssueWhen using a web part in a Nintex form, the web part might fail to load with the following error:Sorry, we had some trouble accessing your site. ResolutionIn Internet Explorer, go to Options > Security and add the following entries to the Trusted Sites:  *.microsoftonline.com  https://auth.nintex.com       

  ISSUE When 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 CODE This page can't be displayed Turn 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. RESOLUTION Contact your Network Administrator to white-list the Nintex cloud host URL mentioned in the error message. ADDITIONAL INFORMATION This is caused by a Network access restrict

IssueWhen attempting to copy a document to a subsite using "O365 Upload File" within a workflow the following error might occur:Details: ServiceNoResponse Description:The list ‘xxxx’ does not exist in web site  ResolutionVerify "Destination site URL" is set to the Subsite URL Verify the user has the appropriate permission to the list Verify that the Folder path exists Save and publish the workflow  

IssueWhen running a workflow that includes a Send an Email action, the workflow will complete successfully, however emails are sent intermittently. ResolutionOpen a support ticket with Microsoft SharePoint support with the Workflow Instance ID of one affected workflow, along with the Start Time and Last Run Time from the Workflow Status page of the instance.  Additional InformationSharePoint Online handles the mail flow for internal emails, as such Nintex does not have any control of email delivery while workflows use the internal mail system of Office 365. 

IssueWhen attempting to open a list item with a Nintex form published, the form errors with - "Input string not in the correct format". ResolutionOpen the Nintex Forms designer Export and save a copy of this form Delete the form Import the form through the designer and publishing. Error Code"Input string not in the correct format" Additional InformationIf this error is occurring via a Nintex Workflow, please check your Nintex Forms that are configured in the Nintex Workflow actions, such as "Assign a Task", and any Nintex Forms published to any content type on affiliated lists (including task lists) or libraries.If step 1 doesn't work because the forms designer cannot be opened, see related links. Related Linkshttps://community.nintex.com/community/build-your-own/blog/2017/02/03/where-nintex-forms-live-in-sharepoint-for-o365 

IssueWhen publishing a Nintex Workflow for Office 365, the follow error occurs:Error publishing workflow. Failure publishing form. Correlation ID: {GUID}Tenant ID: {GUID}Time (UTC): {Date time} ResolutionCheck all the actions within the workflow has been configured properly including the disabled ones.  Make sure that "Run If" actions have at least 1 following action afterwards.  

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 running a workflow that contains an "Assign a task" action, the workflow might hang on that action and not report any error, even if the user account is valid.ERROR CODERESOLUTIONReview regular expressions for a string field that is empty or has a NULL value and add a "Run If" action so the regular expression runs only if the String value input is not empty. ADDITIONAL INFORMATIONThis issue occurs when the "String" field of a "Regular Expression action" contains a value that is NULL or empty.RELATED LINKS

ISSUEWhen trying to save a SharePoint Online site with the Nintex for Office 365 apps installed, the save process fails and the following error occurs:Sorry, something went wrong.  Sorry, this site can't be saved as a template. It contains apps that don't work in templates:Nintex Workflow for Office 365Nintex Forms for Office 365ERROR CODERESOLUTIONRemove the Nintex for Office 365 apps from the SharePoint Online siteNote: With the introduction of the New View Mode in SharePoint Online, it will be necessary to change the view of Site Contents to Classic in order to remove the Nintex for Office 365 appsSave the site as a template Create new site with the saved template Add the Nintex for Office 365 apps back to the SharePoint Online siteADDITIONAL INFORMATIONRELATED LINKS

IssueAfter removing and re-adding one of the Nintex apps within Office 365, the app icon is now missing from the list ribbon. ResolutionRemove the Nintex app that is no longer available in the list ribbon. Once the app is removed, re-add the app to the site. When the app is adding you will see two "ghost" versions of the app, one being added and the other being removed. Cancel the app that is being added to the site, and wait for the "ghost" version of the app to fully remove itself. Once the app is gone from Site Contents, add the app to the site one more time. You will only see one copy of the app within Site Contents (the version being added), and once it has finished adding, the app icon will now be available within the list ribbon. 

QuestionWill Microsoft change MC222880 affect Nintex forms for O365. AnswerMicrosoft is releasing a change that will affect classic form customizations in modern lists and libraries. This change will not affect Nintex Forms for O365.      

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 using a Managed Metadata term value within a text field, such as an email body, or Log To History action, the term displays as 'Value | TermIdGUID'Example: 'Nintex Engineer | b664989e-0ac2-4d49-9a89-d6f7bf092fe1' ResolutionThis is expected behavior when converting a Managed Metadata term to a string. You can use the Regular Expression action with the following configuration to strip out the GUID:String: {Variable:OriginalManagedMetadataTerm} String operation: Replace Pattern: |(.*) Replacement String: Output: {Variable:UpdatedManagedMetadataTerm} 

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 certain Nintex Forms controls, i.e "People Picker", you may observe the following error:“There are unresolved entries”  ResolutionThis occurs when you are using a non-English regional setting, and is a known behaviour. We request users to vote for this change to be implemented via the below link:https://nintex.uservoice.com/forums/218293-4-nintex-forms-for-office-365/suggestions/31337908-missing-auto-generated-translations Additional Information  Related Links  

IssueNintex Workflows will run even when all Start Options are disabled. ResolutionWorkflows require at least one Start Option selected when being published.  Leave "Start manually" set to active and navigate to List Settings > Workflow Settings > Remove, Block, or Restore a Workflow, find the workflow you want to not run, and make sure the No New Instances radio button is selected for that workflow. Additional InformationThe workflow will not run the first time it is published when nothing is selected, however if a start option was selected on a previous published instance, turning off the start options will not prevent it from running. SharePoint Designer workflows cannot even be published without a start option. 

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" 

IssueNintex app(s) are installed on a site and can bee seen in the site contents and are visible on most lists, however they are missing from one list ribbon. ResolutionNavigate to the list If the list is not in Classic view change to Classic view. Click on the cog and select "Edit Page" On the main list web part select "Edit web part" from the top right hand corner black triangle Change the Toolbar Type to "Full Toolbar" Click Apply. From the page tab above the ribbon click stop editing. Icons will now appear on the List ribbon.

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 

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 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 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 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