> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/release-information/flow/6.15/server/6.15.12.md).

# 6.15.12

2024-11-14

#### **Prerequisite**

{% hint style="danger" %}
Before updating the Flow Server to service pack 6.15.12, ensure that the Server Manager Installer is updated to version 6.15.6 or newer.
{% endhint %}

#### **Issues Resolved**

* Resolved memory leak issues in both the REST connector and the Web Service connector.
* Fixed the issue where subscribed workflows did not function correctly with the IFS OData connector. 
* General performance improvements in machine steps, REST connector & Database connectors.
* Fixed multiple issues related to OPC UA connector. 
  * Added support for different authentication methods such as Username & Password authentication and certificate-based authentication.
  * Added support for extension objects both in design time and runtime. 
* Fixed the issue with Infor m3 REST connector error handling. Infor has recently made changes to API v1 where the format/structure of the error message is changed. To handle this in Flow a new configuration named ***Force style for errors*** is introduced in Infor M3 REST connector. 
  * By default ***Force style for errors*** is set to Empty Record. This means the flow will return an empty record in case of an error message returned from Infor M3. The other option is Nil Record and as the name implies the flow will return a Nil record in case of an error message returned from Infor M3.

    <figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FejDl1N1555rGLT1sti1z%2Fimage.png?alt=media&amp;token=8dbf5db2-5a87-40bd-9dcf-4bfaa65f0b1e" alt="" width="447"><figcaption><p>new configuration setting</p></figcaption></figure>

#### **Manual Upgrades**

In some scenarios, the service pack is applied manually without using the installer (e.g. Novacura Cloud customers). In such situations, the Web.config file should be updated manually to include the new dependencies. To update the Web.config,

* Open the Web.config file inside the Server folder&#x20;
* Search for the following entry

  ```xml
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.Extensions.Logging.Abstractions" publicKeyToken="adb9793829ddae60" culture="neutral"/>
    <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0"/>
  </dependentAssembly>
  ```
* and replace it with

  ```xml
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.Extensions.Logging.Abstractions" publicKeyToken="adb9793829ddae60" culture="neutral"/>
    <bindingRedirect oldVersion="0.0.0.0-6.0.0.4" newVersion="6.0.0.4"/>
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-4.0.1.2" newVersion="4.0.1.2" />
  </dependentAssembly>
  ```
* Restart the Flow Server

{% hint style="warning" %}
If you applied service pack 6.15.12 without first updating the Installer, you can resolve the issue by manually updating the Web.config file as outlined in the instructions above.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.novacuraflow.com/release-information/flow/6.15/server/6.15.12.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.