# 2024 04 11 release notes (core)

## Release summary

The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:

**Patchworks core (backend)**

| Release version | Release date    |
| --------------- | --------------- |
| 1.14.0          | 11th April 2024 |

**Patchworks dashboard (frontend)**

| Release version | Release date    |
| --------------- | --------------- |
| 1.11.0          | 11th April 2024 |

New features, updates, and enhancements of note are summarised by product area, below:

* [Marketplace](#marketplace)
* [Process flows](#process-flows)
* [Prebuilt connectors](#prebuilt-connectors)

## Marketplace

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="388">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><p><strong>App install failure</strong></p><p>Fixed an issue where an app would fail to install due to an anomaly in the original creation process. This was a niche scenario around URL parameters not being cleared for  connectors if the connector was changed prior  to the app being uploaded to the marketplace.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/uVJlVUDxjvJi3MgSFEPB">The Patchworks marketplace</a></p></td><td>CPT-2668</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><p><strong>Missing connector information after app install</strong></p><p>Fixed an issue where connector information was sometimes missing for connectors that were installed as part of an app. This happened when the app included a process flow utilising a connector that was uploaded to a private marketplace.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/uVJlVUDxjvJi3MgSFEPB">The Patchworks marketplace</a></p></td><td>CPT-2569</td></tr></tbody></table>

## Process flows

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="388">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="edbc33cea7f34e16b3a205c7a65c3172">New</span></td><td><strong>Track data shape</strong><br>Use this shape to track data, either from a connector source, or a non-connector source (e.g. Inbound API, webhooks, or manual payloads). Tracked data is available for searching from the Process Flow Overview page.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/Y1n6bZHdxkq19kbUGscv">Track data shape</a></td><td>CPT-1536</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Payload variables</strong> <br>Payload variables now support any incoming data format (for example, JSON or text).<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/HC31VdrWhJMUz0LwmCJx">Payload variables</a></td><td>CPT-1322</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><p><strong>Connector shape - configurable retries</strong><br>It's now possible to configure the number of retries (between <code>0</code> and <code>2</code>) that should be made when attempting to make a connection in a process flow. </p><p></p><p>To mitigate connection issues due to rate limiting, you can also define a <code>backoff</code> value (in seconds). <br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/ksVeuo8Bz6ah8fn0PpJx">The connector shape</a></p></td><td>CPT-2333</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>SFTP logging</strong><br>Improved logging information for cases where a specified FTP path cannot be found. <br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/SavR9CxDNdGwueoGB3Ac">SFTP connections</a></td><td>CPT-2702</td></tr><tr><td><span data-option="d8457d8925c74fab90fa132d141b764b">Change</span></td><td><strong>Add to cache shape</strong><br>The way in which <code>flow run</code> caches are cleared has changed. For process flows that are NOT deployed, the cache is cleared in a 2-hour TTL window. However for deployed process flows, <code>flow run</code> caches are cleared as soon as the process flow completes.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/aGi157tdOz4wMkNdBOWh">Add to cache shape</a></td><td>CPT-2370</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Error logging</strong><br>Fixed issue where <code>internal error</code> was being reported following the failure of a flow where there was a valid reason for the failure. HTTP errors are now shown at the end of a failed flow run, including the status code and body of the response from the endpoint.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/RVdm7LuBhWXjhM0Cyuq9">Run logs</a></td><td>CPT-2511</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Run logs scroll</strong><br>Fixed issue where auto-scrolling stopped after 1000 logs. The run logs page now continues to scroll after 1000 entries.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/RVdm7LuBhWXjhM0Cyuq9">Run logs</a></td><td>CPT-2440</td></tr></tbody></table>

## Connector builder

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="388">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="d8457d8925c74fab90fa132d141b764b">Change</span></td><td><strong>Page number pagination method</strong><br>The <code>limit</code> parameter is now optional.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/wFabZBlAIvJY8KiDOqJa">Page number parameter pagination</a></td><td>CPT-2452</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://doc.wearepatchworks.com/product-documentation/release-information/core-release-notes/2024-04-11-release-notes-core.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
