Solution showcase: Learn how to use Nintex CE Platform
This section contains archived Nintex for Office 365 Knowledge Articles.
Recently active
ISSUEWhen attempting to email a shared mailbox via an Office 365 Nintex Workflow the 'Send Email' action is unable to resolve the Shared Mailbox account.ERROR CODERESOLUTIONCheck to see if the email account can receive emails from a different source e.g. Gmail. If the shared mailbox can receive email, then utilize the 'External Email & Attachment' option. If the Shared Mailbox was setup and configured as an Office 365 Shared Mailbox then emails should be received with both options.ADDITIONAL INFORMATIONRELATED LINKS
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
IssueWhen using an action in Nintex Workflow for Office 365 that utilize Connection Manager, this error might occur:Identity Client Runtime library (IDCRL) encounterdd an error while talking the partner STS ResolutionReset the password of the account credentials of the Connection Manager. Additional InformationThe password of the account that is used on Connection Manager has expired.This happened even for the account that has been set to password never expires.
IssueWhen using Office 365 update item permissions action with connection manager, this error might occur:Unable to reach destination server. ResolutionThis is a known issue and has been resolved in the latest version of Office 365 update item permissions action. User required to drag and drop a new action into a Nintex Workflow Designer for Office 365 to get the latest version of the action.
IssueWhen connecting to a database or running an Execute SQL action, the following error occurs:HTTP InternalServerError to https://<domain>.sharepoint.com/<GUIDs>Correlation Id: <GUID>Instance Id: <GUID>Invalid text value.A text field contains invalid data. Please check the value and try again. ResolutionEnsure the Connection String is properly formatted, contains no typographical errors, and is not pointing to a server with a private IP address. Error CodeHTTP InternalServerError to https://YOURDOMAIN.sharepoint.com/ Correlation Id: Instance Id: Invalid text value. A text field contains invalid data. Please check the value and try again. Related LinksConnection String TesterPrivate IPv4 address spaces Wikipedia article
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.
ISSUEWhen attempting to use normal buttons instead of radio buttons with Task Forms, you will get the following error when submitting task:"Error in task. Input string was not in a correct format"ERROR CODE"Error in task. Input string was not in a correct format"RESOLUTIONThis feature is currently not support. However you may wish to vote this feature on our UserVoice page.ADDITIONAL INFORMATIONRELATED LINKS
IssueWorkflows within SharePoint Online will randomly suspend or terminate, and within the Instance Information panel (accessed through the blue 'i' on the Workflow Status page) is the message: 'HTTP status code 429' ResolutionReduce the number of requests that are being made into the SharePoint Online environment by the workflow Review Handling Workflow Throttling Error CodeHTTP status code 429 Additional InformationMicrosoft's documentation on avoiding workflow throttling within SharePoint Online
IssueWhen trying to assign a task to a user, the workflow fails with the error: 'Failed To Resolve User' ResolutionVerify that the user is recognized within the SharePoint Online User Profile Service, and that they have a valid email associated with their profile. Error CodeFailed To Resolve User
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 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.
QuestionHow often do O365 actions retry if they fail to connect to the O365 tenant. AnswerEach query execution has a timeout of 1.5 minutes. The default timeout of the SharePoint SDK (CSOM) is what is usedAll Office 365 actions have the same retry behavior. Additional InformationTo add functionality to the the O365 workflow engine Nintex's Office 365 actions call outside of the tenant to Nintex Infrastructure. The Nintex infrastructure then logs back into the tenant to perform the required activity. Sometimes there can be issues with connecting to the tenant due to a range of issues between Microsoft, Nintex and the Internet. As this is the case Nintex has retry functionality built in so that the workflow does not immediately suspend.
IssueDocument generation is producing documents in an older format of MS Word ResolutionUpdate the document template with the version of MS Word that you want the document to be generated in
IssueNintex O365 Workflow fails to complete once permission has been removed for current item even though the workflow is using Action Step. ResolutionThe solution to this design is to create a new workflow on the same list/library with Start Workflow Action. This action is calling the second workflow which is running under the credentials supplied in the Start Workflow action. This way the second workflow can “see” the item after the permission removal.
IssueWhen attempting to access the Nintex Forms for Office 365 app, the app errors with the message: "User access token redemption failed for site https://SiteURL/ using app with host name formso365.nintex.com 400 (BadRequest) response received from OAuth endpoint." Error CodeUser access token redemption failed for site https://SiteURL/ using app with host name formso365.nintex.com 400 (BadRequest) response received from OAuth endpoint. ResolutionWhite-list *.nintex.com within the firewall that does 'Man in the Middle' encryption/decryption for the corporate network. Additional InformationThis can also result in the Nintex Workflow for Office 365 app hanging on "Connecting to Site."
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 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 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
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
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
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 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 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.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.