Product Forums

Issue DescriptionWhen you use the WFIfElseAdapter Condition action to compare a SharePoint list column, the column reference is treated as literal text instead of the column value. The condition therefore does not match and always follows the negative branch.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the WFIfElseAdapter Condition action and leave one branch empty, the branch is converted without an outgoing line. At runtime, the workflow follows the empty branch and stops, preventing any subsequent actions on that path from running.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you run a workflow that sends emails, the workflow fails and an error occurs.Error Message:The following errors occurs:“Send email failed due to: Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property.”Thereafter,“"no connection string”ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Important Security Update:An important security hardening update was addressed in Fix Pack 33. We strongly recommend that all customers upgrade to this version or a later version to ensure you benefit from this security enhancement.Deprecated functionality and componentsGoogle Chrome intends to deprecate and remove XSLT support from the browser for security reasons. As a result, you may need to migrate your code before support is removed in November 2026.Fix Pack 35 contains the XSLT support for Nintex Automation K2 (5.8). If you cannot install the fix pack on time, you can use a workaround described in XSLT Deprecation in Google Chrome Browser | Community..NET 10 Support Now AvailableInstaller Nintex Automation K2 (5.8) (5.0009.1000.1) is now available here (LINK) and includes support for .NET 10.Please ensure that Fix Pack 35 is also installed, as it includes additional .NET 10 support. IMPORTANT:If you perform a reconfigure without reinstalling the fix pack, users will not be able t

Issue DescriptionWhen you change the font family of a dropdown, the watermark font updates correctly, but its color changes to match the control instead of remaining grey.When you change the font family of a text box or other control, the watermark remains grey, but its font remains Open Sans instead of matching the selected font.When Use Legacy Theme is unchecked, the control and watermark fonts update correctly, but the watermark color changes instead of remaining grey.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you migrate to SPFx, a workflow configured to start when a document is uploaded may start multiple instances for documents that were uploaded previously and already have a K2 workflow instance running. The workflow then stops starting new instances for newly uploaded documents.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you host your K2 database on Azure SQL, you may experience high CPU usage on a SQL instance.ResolutionThe fix is available in:Nintex Automation K2 (5.8) Fix Pack 37.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Hi everyone,I’m currently developing a workflow in Nintex K2 and I need the workflow to retrieve data from a SharePoint Online list.I’m quite new to K2 and I’m not sure what the correct integration/setup process is between K2 and SharePoint.My requirement is basically:SharePoint Online List → K2 → SmartObject → K2 WorkflowI would like to use the SharePoint list data inside the workflow, for example to retrieve/list items and use the column values in the workflow.I have access to K2 Management, and I can see SharePoint-related Service Types such as SharePoint Site Collection and K2 for SharePoint, but I’m unsure which one should be used and how it should be configured.My main questions are:What is the recommended way to connect K2 to an existing SharePoint Online site/list? Do I need to create a Service Instance in K2 Management using the SharePoint site URL? Which SharePoint Service Type should be used? What authentication method should be configured for SharePoint Online? Does K2 for

In NWC I need to create an xtension using api v3.all the posts I’m seeing suggests that NWC can’t utilise v3 at the moment.is this the case or am I just configuring the xtension wrong?. I keep getting an error saying the specification is incorrect. cheers marc

Important Security Update:An important security hardening update was introduced in Fix Pack 29. We strongly recommend that all customers upgrade to this version or a later version to ensure you benefit from this security enhancement.Deprecated functionality and componentsGoogle Chrome intends to deprecate and remove XSLT support from the browser for security reasons. As a result, you may need to migrate your code before support is removed in November 2026.Fix Pack 30 contains the XSLT support for Nintex Automation K2 (5.7). If you cannot install the fix pack on time, you can use a workaround described in XSLT Deprecation in Google Chrome Browser | Community..NET 10 Support Now AvailablePlease ensure that Fix Pack 30 is installed if you are using .NET10, as it includes all necessary support.IMPORTANT:If you perform a reconfigure without reinstalling the fix pack, users will not be able to log into Nintex Automation Designer/Manager/Workspace/Runtime after the reconfigure completes and t

I’m working on a flow to update a Nintex Table from a report retrieved from our ERP. Part of the flow requires that it compare a ticket number from each row of the report to what’s already in the table, so it will only add new rows.The approach I’m using is to use a Query a Table action to generate a collection of only the ticket numbers (i.e. theTableResult>Rows) then using a Check If Item Exists in Collection action from a ticket number in the report, to see whether a given ticket number is in the collection and hence in the table.The snag I’ve run into is that the Check action doesn’t seem to be correctly evaluating whether the supplied value is found in the collection. This is what the collection looks like in Log to Instance Details, along with the raw result of the Check action for ticket 71629 (supplied as a default text variable):Logging the First Row from that same table query appears to show the value correctly:In other words, it seems to work fine showing the info directl

I’m trying to generate a text variable with a custom date.I can’t use “Format date from String”: none of the built-in “Format” options match what I need.I’d prefer NOT to use a form (this will be a component workflow, invoked from an external app), so I’m not sure this documentation applies:  https://help.nintex.com/en-us/nwc/content/designer/Functions/formatDate.htmThis is EXACTLY what I’m looking for: yyMMddHHss:  I’m trying to use fn-FormatDate({Workflow:Current Date and Time},"yyMMddHHmm") in “Set Variable”.It’s printing out “fn-FormatDate(...)” instead of executing the inline function:Q: What am I missing??? BACKGROUND:What brought the question up is that I was trying to do several SMALL tasks that I THOUGHT were “trivially simple”: a) format a custom date string (this question), b) generate a random number, c) create a text file formatted with embedded newlines, d) etc. etc.I found this “workaround” for the custom date string:1. Call Format Date Time with one of the built-in form

Hello,Just have question about Nintex workflow “Assign Flexi Task” not sure if that was the expected behaviour. I have setup a workflow with “Assign Flexi Task” for some reason when I rejected the assign task it does not go to the next step where it send email. The Approve outcome works but not Reject.   

Issue DescriptionWhen you install a fix pack on a K2 5.9 environment with the Client Tools installed, navigating to any K2 site displays a "Configuration Error" screen.Error Message:The following error occurs:“Server Error om ‘/Management’ Application.”ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 16.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you migrate from Exchange Online EWS to Microsoft Graph for Send Mail workflow actions, the Send Mail action fails when the configured From address is a mailbox other than the default K2 service account mailbox.Error Message:The following error occurs in the HostServer log:“Code: ErrorItemNotFoundMessage: The specified object was not found in the store., The process failed to get the correct properties.”followed by:“ServerEvent: There is no connection string for the destination email address”ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 16. Nintex Automation K2 (5.8) Fix Pack 37.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the PUT method to upload files to SharePoint Online, PDF files are uploaded and displayed correctly. However, other file types appear to be saved but are corrupted and cannot be viewed.When you change the method from PUT to POST, an error occurs.Error Message:The following error occurs:“404 {"error":{"code":"itemNotFound","message":"The resource could not be found."”ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 16.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

.

Important Security Update:An important security hardening update was addressed in Fix Pack 01. We strongly recommend that all customers upgrade to this version or a later version to ensure you benefit from this security enhancement.Deprecated functionality and componentsGoogle Chrome intends to deprecate and remove XSLT support from the browser for security reasons. As a result, you may need to migrate your code before support is removed in November 2026.Fix Pack 02 contains the XSLT support for Nintex Automation K2 (5.9.1). If you cannot install the fix pack on time, you can use a workaround described in XSLT Deprecation in Google Chrome Browser | Community..NET 10 Support Now AvailableInstaller Nintex Automation K2 (5.9.1) (5.0010.2000.1) is now available here (LINK) and includes support for .NET 10.Please ensure that Fix Pack 03 is also installed, as it includes additional .NET 10 support. IMPORTANT:If you perform a reconfigure without reinstalling the fix pack, users will not be ab

Issue DescriptionWhen you enter content that exceeds the available field length in Workflow Designer, a horizontal scroll bar is displayed at the bottom of the field. However, the scroll bar height and behavior is inconsistent between versions.ResolutionThe fix is available in:Nintex Automation K2 (5.9.1) Fix Pack 04. Nintex Automation K2 (5.9) Fix Pack 16.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you are creating or editing a workflow in the Designer, the Operator filter for SmarObjects under Functions is not visibleResolutionThe fix is available in:Nintex Automation K2 (5.8) Fix Pack 36. Nintex Automation K2 (5.9.1) Fix Pack 04.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

We recently migrated a K2 5.9 FP14 system from EWS Online to Graph and noticed issues with mails.The mails for tasks and redirects are not going through but email action ones are, has anyone had a similar issue with Graph and found a solution?We checked the HostServer and Event View logs, but no errors are showing up.

Follow this guide to use Python of a different version from what is bundled in Nintex RPA. Skip Step 1 if you already have Python installed Step 1. Install Python Option 1:  Install using an exe installer of your prefered version - https://www.python.org/downloads/windows. Option 2: Install using ChocolateyFirst, follow the instructions here to install Chocolatey - https://chocolatey.org/install Then, to install Python, open Powershell in Administrator mode and run choco install python -y Step 2: Replace the bundled PythonFor Studio.- Go to C:\Program Files\Nintex RPA Studio (or the location where Studio installed). Backup and remove Python folder.- Go to the location where your copy of Python is instaled, e.g  C:\Python314. Copy the Python folder into Studio and rename to Python.For Robot- Refer to the steps for Studio above. Robot may be installed at C:\Program Files\Nintex RPA Robot  You may verify the change by running the Run Script AC and print the Python version.If you prefer to

Hello Nintex Community, I would like to know if there are any plans on the Nintex Automation Cloud roadmap to introduce:A native Workday connector for integrating with Workday HR and Finance systems. A Data Lookup capability similar to lookup actions available for other enterprise applications, enabling users to retrieve and reference Workday data within workflows, forms, and automation processes.We are exploring broader HR process automation scenarios and would be interested in understanding whether native Workday integration is being considered, or if there are any recommended approaches currently available through Xtensions, APIs, or third-party connectors.Any information on future roadmap plans, current alternatives, or best practices would be greatly appreciated.Thank you!

Hello!  Just curious if anyone at Nintex has any updates as to when Tables might receive API support?  We have a few different processes that would benefit from making the use of Nintex Tables over their current system, but we would really need the ability to read/write to the Nintex Tables from external systems before that’s possible.  2 years ago, we were told it was coming - I’m just hoping for an update on when. Thank you!

Dear Team,I am writing to request your assistance with an issue I am encountering while working with our mock SAP setup. Please find the details below, along with the attached Swagger file for your review.---1. Context- We are using the attached Swagger file to create a mock SAP environment.- I am using Nintex Workflow to retrieve data from this mock SAP via the defined API endpoints.2. Issue DescriptionWhen I retrieve data for a specific object (e.g., object code OC"), the HTTP response returns a "value" field that contains two (2) items. However, instead of mapping each item into its corresponding column, the system displays the entire "value" array as a single combined string in one field.Expected behaviour:| Column | Data || Value 1 | Item 1 from the response || Value 2 | Item 2 from the response |Actual behaviour:| Column | Data || Value 1 | Item 1, Item 2 (both items combined) || Value 2 | Item 1, Item 2 (both items combined)|In summary, the data is not being itemised or segregat