Archive: Nintex for Office 365 Knowledge Articles

ISSUE When 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 ERROR CODE RESOLUTION Verify "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  ADDITIONAL INFORMATION 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

IssueWhen completing a Nintex Task Form associated with a Nintex Workflow, SharePoint displays the error message "Unexpected error occurred." ResolutionMake sure the task form has the "Task Outcome" control present or SharePoint will throw an error message when closing the form. 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. 

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 using an email action such as Send email or Assign Flexi Task, and using {Workflow Context: Current Item Url} in the body of the email, the hyperlink is broken in the email sent to the recipients.ERROR CODERESOLUTIONOption 1Remove any spaces in the list name and run the workflow. Option 2 Click on Insert link in the body of the email. Enter the URL { Workflow Content: Current Item Url}. Enter the hyperlink text  - "Hyper link text to be displayed in the email body".ADDITIONAL INFORMATIONDepending on the email client, this might be displayed as a clickable hyperlink. If there is a space in the link, then it might be broken after the space, if the email client cannot handle the space. Outlook will try to resolve this text as a URL, but Outlook Web Access will display it as text and not a URL.RELATED LINKS

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 running a workflow, it might stop automatically and an error similar to the following might occur: RequestorId: eXXXXea-1164-652d-0000-000000000000. Details: System.Activities.Statements.WorkflowTerminatedException: The instance has been moved from the Suspended state to the Terminated state because it has expired. The original error which caused it to be Suspended is: The instance has exceeded the outbound http request quota for a 1.00:00:00 time period. The 5000 request limit was reached in 01:23:53.7820143 Error Code"The instance has exceeded the outbound http request quota for a 1.00:00:00 time period. The 5000 request limit was reached in ."Or “RequestorId: eXXXXea-1164-652d-0000-000000000000. Details: System.Activities.Statements.WorkflowTerminatedException: The instance has been moved from the Suspended state to the Terminated state because it has expired. The original error which caused it to be Suspended is: The instance has exceeded the outbound http request quota f

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 a responsive form has a confirmation message and redirects to a specified URL, the form will hang when using the Save button within the ribbon of the form. ResolutionThis is a known defect with the current release of Nintex Forms for Office 365.Using the Save button on the form itself does not cause this behavior. 

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 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 viewing the workflow status column, workflow progress is not displayed.ERROR CODERESOLUTIONExport all workflows on the list to a secure location. Recreate the list. Import all workflows and publish the workflows.ADDITIONAL INFORMATIONThis issue is caused by using a list template that had the workflow status column already created before the list was saved.RELATED LINKS

ISSUEAfter deleting a control with a button that calls JavaScript, the following error occurs:An embedded page at formso365.nintex.com says:There are some problems with the design of this form and this is causing some errors. Please contact the designer of this form to rectify these.The form is reporting the following errors:<control name> is not definedThis error persists even after deleting the form and creating a new version with the default SharePoint form.ERROR CODERESOLUTIONIn SharePoint designer, navigate to the site > All Files > Lists > ListName > Item. Delete the NFForm.xml file. Navigate to https://tenanturl/site/NintexFormXml. Find and delete the file that contains the matching List GUID. Create a new form in the designer.ADDITIONAL INFORMATIONNintex Forms stores two copies of the form and they can conflict with each other. Deleting both copies of the form resets the form completely.RELATED LINKS

ISSUEWhen accessing a Nintex form, the following error occurs:Unable to get property 'value' of undefined or null reference FormsPart.aspxERROR CODERESOLUTIONIn the FormPart.aspx JavaScript to get the value from the single line textbox control, locate the following line of code:NWF$(".option_crId_control .nf-filler-control-inner")[0].firstChild.dataAnd update it as follows:NWF$(".option_crId_control .nf-hidden-associated-control").val()ADDITIONAL INFORMATIONRELATED 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. 

ISSUEWhen creating a list with geo-location fields, items using those fields cannot be viewed and the following error occurs:Index was outside the bounds of the array. If the problem persists, contact your support team with the following information:ERROR CODERESOLUTIONThis issue is currently under investigation. As a workaround, try the following:Navigate to Site settings. Regional settings. Select the Time zone and change it to something other that what is shows and wait for changes to take place. Once the time zone is set, set it back to your current time zone.  Once you have confirmed its changed back, go back to the list and form and try to access the item again.ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen setting the value for a Choice control on the form, the value is not being saved or reflected in the connected column on the list.  ResolutionVerify that there is only one Choice control connected to the choice field on the list. If there is more than one connected control, the value from the lowest control on the form (closest to the bottom of the form) will be saved back to the list, and as such reflected back into the higher control on view or edit of the from. 

IssueWhen sending an email to a large group of recipients, the recipients receive duplicate emails and the workflow fails to continue. ResolutionEnsure that the batch of recipients being submitted to the action is below 200.  Additional InformationThe issue can be caused by the number of user accounts being referenced by the action. 

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

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 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 using Office 365 Upload File action to update a Person or Group field, the following error occurs: ‘Error performing Office 365 upload file activity. Reason: There was a service parameter validation error. Error: Some parameters failed the validation check.Validation error 1 - InputMetaDataXml. Reason: The 'Fields' is invalid.’  Resolution'Office 365 Upload File' action does not support update to a 'Person or Group' fields. As a workaround, utilise the 'Office 365 update items' action to update 'Person or Group' fields.