Archive: Nintex for Office 365 Knowledge Articles

ISSUEWhen a workflow uses the Send An Email action and sends the email via the External Email and Attachment option, the email never arrives at the external email.ERROR CODERESOLUTIONVerify that the email can be sent to via an email service outside of Nintex Workflow. Verify that the email can be sent to via an email service outside the corporate environment. Verify that "noreply@workflownotification.com" has not been blacklisted for that email environment. If the issue persists contact support@nintex.com and ask to verify the domain has not been restricted for the external email service.ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen trying to add one of the Nintex for Office 365 apps to a SharePoint site, the app addition fails and the following error occurs:Something went wrong trying to add app. Click to retry. When trying again, the app addition fails again with the same error. ResolutionContact SharePoint Online support and request to have the app site manually cleared from Azure. 

IssueWorkflow gets stuck when trying to create documents using custom templates with Create List Item Or Document Set Action. ResolutionSave and close the template document if it has been opened from the SharePoint library. Otherwise this will cause the workflow to become stuck and not progress as the template file is still open by a user. 

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 execute the workflow with a Send an Email action configured with body of email  to get the information from User Profile properties, this error might occurs:RequestorId: xxxxxxxx-xxxx-xxxx-0000-000000000000. Details: System.Activities.Statements.WorkflowTerminatedException: {"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access denied. You do not have permission to perform this action or access this resource."}}} ResolutionGrant permission to the user profile service Error CodeRequestorId: 6fbca847-0c8a-0cde-0000-000000000000. Details: System.Activities.Statements.WorkflowTerminatedException: {"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access denied. You do not have permission to perform this action or access this resource."}}} Additional InformationAccess to the User Profiles service is required for use of the following manager references in workflows.Manager displ

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 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 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 attempting to open a form not using the global admin account you get the following error: "This content cannot be displayed in a in a frame."This only occurred in IE when opening a form configured to open in a dialog box. When changing the configuration to not use a dialog box the form opens fine.  ResolutionAdd the following sites to Trusted Sites:- *. nintex.com (https://nintex.com/) - *. sharepoint.com (https://sharepoint.com/) - *. nintexo365.net (https://nintexo365.net/) *.office.com*.microsoftonline.comIf the above doesn't resolve the issue, access internet options, security settings - trusted sites Zone, advanced settings. Search for "Launch programs and Files in an IFRAME" If Prompt is select change the setting to enable. 

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

IssueWorkflow instance fails with the error: System.Activities.Statement.WorkflowTerminatedException: Error Code: -2146232060, Microsoft.SharePoint.SPException, Message: Exception from HRESULT: 0x80131904 ResolutionPlease open a support ticket with Microsoft SharePoint Online support, as this issue will fall outside the control of Nintex on the SharePoint Online platform. Error Code-2146232060, Microsoft.SharePoint.SPException, Message: Exception from HRESULT: 0x80131904 Additional InformationThis error is caused by a failure within the SQL database system of the SharePoint Online environment. 

  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 using Office 365 Create List Item or Document Set action for a Document Library with Document Set configured  and the Library has been renamed, this error might occurs:Folder for the new list item does not exist or the current user lacks permissions to the folder.  ResolutionThe issue has been identified and has been fixed on the latest Apps of Nintex Workflow for Office 365. Make sure the Nintex Apps has been updated into latest version. Manually Update O365 Apps. Drag and drop a new "Office 365 Create List Item or Document Set" to the workflow designer.  

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

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 double-clicking a control to open the Control Setting and Setting section located on the right side of Nintex Form Designer for Office 365, the control setting and setting section does not load or appears blank.  ResolutionReset the Nintex Form by clicking the "Reset" button in the Nintex Form Designer ribbon.  Additional InformationThe root cause is one of the control or rules or validation or formula is incorrect or corrupted.  

IssueA '404' page error occurs when closing, submitting, or saving a Nintex Form. Resolution1. Open the form in the Nintex Form designer2. Open the settings for the button control.3. Navigate to Advanced > Redirect URL4. Ensure that the 'Redirect URL' is a valid address. Note: This field is blank by default. 

Issue When 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.    Resolution This 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 trying to publish a Nintex workflow within Office 365, the workflow fails to publish and the following error occurs:Error publishing workflow. The request message is too big. The server does not allow messages larger than 2097152 bytes.ERROR CODERESOLUTIONRemove any unused actions within the workflow design. If there are no unused actions within the workflow design, the workflow will need to be split into multiple parts.ADDITIONAL INFORMATIONRELATED LINKSSplitting large or complex workflowsUpload large files sample add-in for SharePoint

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 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 'Set Workflow Variable' in Nintex Workflow for Office 365, this error might occur during workflow runtime:RequestorId: <GUID>. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.InvalidCastException ResolutionMake sure that variable type and the value used to set the workflow variable matches. For example: A Date/Time type of variable would not match with Number value. 

ISSUEWhen attempting to publish an Office 365 Nintex workflow, the following error might occur:  Error publishing workflow. Column ' ' does not exist. It may have been deleted by another user.ERROR CODEError publishing workflow. Column ' ' does not exist. It may have been deleted by another user.RESOLUTIONExport the workflow file, and then re-import and publish the workflow to recreate the missing columns.ADDITIONAL INFORMATIONThis is caused by a conflict between an open InfoPath Form, and Nintex workflow designer.  If there is a published InfoPath form, and the InfoPath designer is not closed while workflows are published and run; InfoPath cannot reconcile the list columns held in memory, and the list columns created through the new workflow, and as such removes the list columns from the SharePoint list. The deletion of the columns results in the workflow no longer being able to publish, throwing the error above. To avoid this, please make sure that InfoPath is closed when publishing

ISSUE When attempting to publish a workflow within the Nintex Workflow for Office 365 designer, the workflow fails to publish and the following error occurs in the designer: Error publishing workflow. Object reference not set to an instance of an object. ERROR CODE RESOLUTION From the ribbon within the workflow designer, open the Variables menu. Identify the variables with Initiation set to Yes that are of Integer type. If any of the identified variables are not currently in use, delete and re-create them.  Note: If this was all of the identified variables, you should now be able to publish successfully. If any of the identified variables are currently in use they will have to be manually updated within the workflow definition by Nintex Support. Export the workflow file and send it to support@nintex.com with the identified variables ADDITIONAL INFORMATION RELATED LINKS