Archive: Nintex for Office 365 Knowledge Articles

ISSUEWhen creating a new workflow in Nintex Workflow for Office 365, a "For development use only" message appears in the background.ERROR CODERESOLUTIONThis is by design. Workflows will be marked as 'For development use only' until the workflow has been assigned to production on publishing. For more information, see How to Designate a Production or Development Workflow in O365.ADDITIONAL INFORMATIONRELATED LINKS

ISSUEWhen browsing to Nintex Forms using Safari on Mac, the following prompt appears:Please enable cookies for your browser to use the FormERROR CODE‘Please enable cookies for your browser to use the Form’RESOLUTIONNavigate to Safari > Preferences. Click Privacy. Select "Allow from websites I visit" or "Always allow".ADDITIONAL INFORMATIONForms is using cookies for user authentication, this is part of the product and cannot be changed. The reason Safari (default behaviour on OS X and iOS) behaves differently than Chrome is because Safari defaulted to not accept all cookies, while Chrome does. As such this would be considered expected behavior. RELATED LINKSSafari 8 (Yosemite): Manage cookies and website data

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

IssueCannot see the Nintex Workflow or Nintex Forms for Office 365 app within Site Contents even after adding the app to the tenant from the SharePoint Online store. ResolutionOpen Office 365 Admin panel Open SharePoint Online Administration Open the Apps menu Open Mange Licenses Select the drop-down arrow next to the Nintex Workflow for Office 365 or Nintex Forms for Office 365 section, and select Manage License Select the ACTIONS control drop down and select Recover License Select Continue and then Return to Site 

IssueAfter configuring the Send Email action, when selecting save the action errors with:Oops! Something went wrong. Email - dispose : TypeError: Object expected Error CodeOops! Something went wrong. Email - dispose : TypeError: Object expected ResolutionUse a browser other than Edge for workflow design, as it is not supported by Nintex for Office 365.  Related LinksNintex Workflow Supported Browsers 

IssueWhen tying to publish a workflow within Office 365, the designer presents the following error after selecting Publish:Error publishing workflow. System.Net.WebExeption: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. Error CodeError publishing workflow. System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult) --- End of inner exception stack trace - ResolutionOption 1:If the site was recently migrated, please remigrate the site and that should resolve the issue.Option 2:If the site was not recently migrated, please contact M

ISSUEWhen a workflow contains an action(s) that utilize Connection Manager, the following error may occur: The username format is invalid.ERROR CODERESOLUTIONConfigure the Username field, in the Connection, with an email address instead of a display name. ADDITIONAL INFORMATIONRELATED LINKSHelp file - configure a connection manager

IssueNintex Workflow for Office 365 is does not load and shows a spinning circle.Furthermore from the Browser Developer Tools (F12)> Network tab, the following error may appear:Field type [field name] is not installed properly. Go to the list settings page to delete this field ResolutionVerify if the "Field type" mentioned on the error message exists and delete it as per error message advised. Contact Microsoft Support for guidance if you are unable to find or for any further details regarding the mentioned "Field type". Additional InformationThe field type mentioned does not belong to Nintex, therefore contacting Microsoft Support is recommended.  

ISSUEWhen saving a Nintex Workflow in Office 365, the following error might occur: Variable - dispose : TypeError: Object expectedERROR CODEVariable - dispose : TypeError: Object expected errorRESOLUTIONAs a tenant administrator, click the gear icon on the top right of the Nintex Workflow Designer window. Click Grant Access to Workflow.ADDITIONAL INFORMATIONFor more information, see Assign a task action for Nintex Workflow for O365 throws error on save.RELATED LINKS

ISSUEWhen publishing a workflow, the following error might occur:Error publishing workflow. Workflow XAML failed validation due to the following errors: The private implementation of activity '1: DynamicActivity' has the following validation error: Value for a required activity argument 'TargetListId' was not supplied. HTTP headers received from the serverERROR CODEError publishing workflow. Workflow XAML failed validation due to the following errors: The private implementation of activity '1: DynamicActivity' has the following validation error: Value for a required activity argument 'TargetListId' was not supplied. HTTP headers received from the serverRESOLUTIONRecreate the Query List actions in the workflow. Republish workflow.ADDITIONAL INFORMATIONRELATED LINKS

ISSUEWhen using Office 365 storage on a subsite, the following error might occur:AADSTS50001: The application named <application name? was not found in the tenant named <tenant ID>. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant.  ERROR CODERESOLUTIONDocuments can only be stored at the site collection level.ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen using the List Lookup control on Nintex Mobile that is connected to an Office 365 list, it will only return a total of 2000 items, regardless of the number of items on the list.ResolutionMake sure the Nintex forms and Nintex Mobile are all updated to the latest version. This has been resolved on the latest version of the product.  

IssueWhen adding Nintex Workflow or Nintex Forms for Office 365 apps to a site, they show as "Pending Purchase" instead of being added to Site Contents. ResolutionThe apps are pending approval within the SharePoint Online environment and must be approved by the SharePoint tenant administrator. For more information, see Request app installation permissions in Microsoft Support.  

IssueWhen using the Task action in Nintex Workflow for Office 365 with the "Auto-complete task" setting being activated, the user finds the "task date completed" is the same date when the task created, this can be confusing as to when the Task was actually completed.  ResolutionMake sure to get the information on the task last date modified from the task itself (via workflow task list) and not from the item related to the task.  Additional InformationUse the Query List action by supplying the Task ID from the Task action output, to get the information details of the completed Task. 

ISSUEWhen loading a Nintex Form, the following error occurs, even though app is already up to date:The app Nintex Forms for Office 365 is out of date.  Please update the appERROR CODERESOLUTIONCheck the Javascript on the form to ensure that all parentheses () and brackets {} have been closed.ADDITIONAL INFORMATIONWhen a parenthesis or bracket is not closed it breaks the formatting of the form and the form fails validation. Ensuring all brackets and parentheses are closed properly in the Javascript should resolve this issue.RELATED LINKS

IssueDuring a data center migration the customer receives the following error when publishing a workflow.“Workflow starting based on conditions cannot be saved or published until migration is complete”. Error CodeWorkflow starting based on conditions cannot be saved or published until migration is complete ResolutionThere are multiple steps to a data center migration and one of them is to migrate workflow start condition subscriptions.Each start condition requires a subscription in the list that they are being published on.Each list can hold a total of 100 subscriptions.If these subscriptions are taken up by other applications such as Microsoft Flow the customer will receive this error.Resolutions.1. The customer will need to manually delete subscriptions from the list to make room.2. The customer can remove all start conditions from the workflow and then publish.3. Worst case scenario is that DevOps can remove the subscriptions from the source data center so that they do not need to b

ISSUEWhen saving a workflow, or configuring workflow actions, in Nintex for Office 365, using Edge browser, the following error occurs:Email = dispose : TypeError: Object expectedERROR CODERESOLUTIONUse a different browser. For more information, see Nintex Forms Supported Browsers. ADDITIONAL INFORMATIONEdge is currently not a supported browser.RELATED LINKS

IssueWhen sending emails using the Send An Email action in an Office 365 workflow, the emails have a blank subject line when received by recipients. ResolutionWhen using an Advanced Lookup within the subject line field, do not copy and paste them from one Send An Email action to another. Re-type the subject line and re-use the Advanced Lookup control to pull in the lookup value. 

IssueWhen Submitting a Nintex Form, the following error may occur: hexadecimal value 0x0B, is an invalid character ResolutionMake sure to type all the values for the Form. If the user requires to copy and paste the values from another source then please do paste the values into Notepad. After that, copy the values from the Notepad into the Nintex Form. Additional InformationThis error is because the submitted value contains a special or unknown character such as "[ ]" when a content has been copied from another source such as Words, PowerPoint, Website content, etc.  

IssueWhen publishing a Nintex Workflow the error "The workflow name is used elsewhere on this site. Please choose another name.” occurs.When looking through the site there is no existing workflow with the name that is being used when publishing. Error CodeThe workflow name is used elsewhere on this site. Please choose another name. ResolutionSolution 1.Empty the SharePoint recycle bin.Publish workflow.Solution 2.Log into the Site of the O365 tenant with SharePoint Designer.From the Objects tab in SharePoint Designer click Workflows.Find the Workflow with the name that you are wanting to use and delete it.Publish your workflow. Additional InformationThis issue can occur when a list has a Nintex Workflow published on it and the list is deleted without deleting the workflow from the gallery first.This same error will occur when creating a workflow with SharePoint Designer as the error is coming from SharePoints Workflow Manager and not Nintex. 

IssueWhen uploading a document to a document library in SharePoint Online that has a Nintex Form published, Internet Explorer presents a window that states "This content cannot be displayed in a frame". Resolution In Internet Explorer, please navigate to Settings (Cog in top right) > Internet Options > Security > Trusted Sites > Sites and add the following sites:*.office.com*.microsoftonline.comYou may need to close and reopen Internet Explorer for this to take affect. Error Code"This content cannot be displayed in a frame" Additional InformationThis appears to only occur when there is a SharePoint Column that is 'Required'. 

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 responding to a Lazy Approval task notification, the following error might occur:Your response to this task was not able to be interpreted. The following phrase is invalid. ResolutionOnly reply with the valid phrase on a line by itself at the top of the email. 

IssueThe Save button is disabled and user unable to Save the Task action configuration.  ResolutionCheck the Content Type in use, if custom content type is utilized then try to remove the existing content type and use the default instead.  If the issue with Custom Content Type, then make sure that the custom content type has been configured properly.  

IssueWhen an external email address is configured in a Assign a Task workflow action, the following error occurs:Sorry, we're having trouble reaching the server  ResolutionConfigure the Assign a Task action with an email address within the Office 365 tenancy. Additional InformationEmail recipients in Assign a Task action are restricted to those with email accounts in the Office 365 tenancy. Related LinksHelp File - Assign a Task