Nintex Automation K2 Updates & Fix Packs

Important Security Update:An important security hardening update was addressed in Fix Pack 13. 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 14 contains the XSLT support for Nintex Automation K2 (5.9). 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) (5.0010.1000.1) is now available here (LINK) and includes support for .NET 10.Please ensure that Fix Pack 15 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

Issue DescriptionWhen you create a REST Service Instance using a Swagger/OpenAPI specification, a required string parameter such as issueKeyOrId in the /api/jira-api/v1/issue/{issueKeyOrId} endpoint is generated as an Object in the SmartObject instead of Text/String. When you enter a string value, the SmartObject returns an error because an Object value is expected.Error Message:The following error occurs:“SourceCode.SmartObjects.Services.Endpoints.Rest.Exceptions.RestDeserializationException: Unable to deserialize value.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 a workflow variable of type Date and Time, the converted workflow cannot be deployed. Saving fails with a Bad Request, without indicating the cause in the designer. This occurs whether or not a default value is set for the variable.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 NWSwitchAdapter Switch action and leave a branch empty, the branch converts without an outgoing line. At runtime, the workflow follows that branch and stops, preventing 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 use the NWBuildStringAdapter Build String action, the composed text is converted as literal text. References such as {ItemProperty:Title} and {Common:CurrentDate} are not resolved, so the variable contains the reference text instead of the actual values.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 SPSetFieldWithKeyAdapter Set Field Value or SPUpdateItemWithKeyAdapter Update List Item action, the step converts without the list, method, or column bindings. The step completes successfully at runtime but writes nothing to the list, and references in the value are treated as literal text.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 NWSendMessageAdapter Send Notification action with a hyperlink in the message body, the link is carried across as raw markup and cannot be displayed by the designer's body editor, causing the message body to appear empty.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 NWSendMessageAdapter Send Notification action with the {Common:AllApproverComments} reference, it converts to an unmapped placeholder. K2 has no equivalent comments field, so the placeholder cannot be mapped or used.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 NWSendMessageAdapter Send Notification action with a person selected directly in the recipient field, the recipient is exported as a SharePoint claims login and passed as plain text. K2 cannot resolve the recipient, so the notification is not sent.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 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.

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

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.

Issue DescriptionWhen you install Fix Pack 34 on an environment where the database is not named K2, an installation error occurs.Error Message:The following error occurs: “Script execute failed: System.Exception: Script execution exception: System.Data.SqlClient.SqlException: Invalid object name 'K2.SmartBroker.ServiceType'.”ResolutionThe fix is available in:Nintex Automation K2 (5.8) Fix Pack 35.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 Condition action ‘WFIfElseAdapter’, it has no conversion mapping and falls back to a generic placeholder step instead of converting to a K2 Decision.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 15.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.