# 2026 02 04 release notes (core)

## Release summary <a href="#release-summary" id="release-summary"></a>

This page summarises items scheduled for the following release to the Patchworks Core Production environment.&#x20;

| Release version | Release date                      |
| --------------- | --------------------------------- |
| v2026-02-04     | Wednesday 4th February 2026 (a.m) |

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

* [Analytics](#process-flows)
* [Process flows](#process-flows-2)
* [Virtual environments](#virtual-environments)
* [Connector builder](#connector-builder)
* [User management](#user-management)

## Analytics <a href="#process-flows" id="process-flows"></a>

<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="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="edbc33cea7f34e16b3a205c7a65c3172">New</span></td><td><strong>Conjura analytics</strong><br>Patchworks has partnered with Conjura to deliver advanced analytics. If you use (or want to use) Conjura for data analytics, you can now select an <code>analytics</code> menu option from the Patchworks dashboard, to log in/sign up.<br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../company-management/company-insights/patchworks-advanced-analytics">Patchworks advanced analytics</a></td><td>CPT-5147</td></tr></tbody></table>

## Process flows <a href="#process-flows" id="process-flows"></a>

<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="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Try/catch shape - placement</strong><br>Fixed an issue where the <code>try/catch</code> shape was not triggered if no payload was received. The fix ensures that a <code>try/catch</code> can now be placed at the very start of a flow, before data is received.<br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../process-flows/building-process-flows/process-flow-shapes/standard-shapes/try-catch-shape">Try/catch shape</a></td><td>CPT-4584</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><p><strong>Try/catch shape - execution failures</strong><br>Fixed an issue where failed payload meta responses exceeding the maximum size could result in failure to execute the <code>try/catch</code> shape.<br><br>Similarly, if no <code>try/catch</code> was present but <a href="../../process-flows/building-process-flows/process-flow-settings">the flow was set to remove failed payloads</a>, an error was generated, and the flow failed.</p><p></p><p>Now, in this scenario, the associated meta response is truncated, so the flow can continue normally. Run logs indicate where data was truncated, and if the original payload was also removed to meet the maximum meta response size limit.<br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../process-flows/building-process-flows/process-flow-shapes/standard-shapes/try-catch-shape">Try/catch shape</a></p></td><td>CPT-5001</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Connector retry &#x26; backoff behaviour with try/catch</strong><br>Fixed issues where connector shape <code>retry</code> and/or <code>backoff</code> settings were not working as expected when present in a <code>try/catch</code> path.  <br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../process-flows/building-process-flows/process-flow-shapes/standard-shapes/connector-shape">Connector shape</a></td><td><p>CPT-5008</p><p>CPT-5056<br><br></p></td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Connector shape - backoff setting not retained</strong><br>Fixed an issue where the <code>backoff</code> value for a connector shape was not always retained after saving shape settings.<br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../process-flows/building-process-flows/process-flow-shapes/standard-shapes/connector-shape">Connector shape</a></td><td>CPT-4989</td></tr></tbody></table>

## Virtual environments

<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="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><p><strong>Deployment history</strong><br>When viewing deployments via the flow deployments page or from a <a href="../../virtual-environments/accessing-virtual-environments/the-anatomy-of-a-virtual-environment">virtual environment</a>, you will now see one entry for every deployment (previously, only the current deployment was displayed).</p><p></p><p>For example, if a single process flow is updated and deployed four times, four deployment records will be shown. <br><br>Note that historic deployments made before 4th February 2026 will not be shown.<br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../virtual-environments/managing-virtual-environments-versions-and-flows/managing-virtual-environment-flow-deployments/viewing-flow-deployments">Viewing current flow deployments</a></p></td><td>CPT-5095</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="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Next page URL pagination - relative URLs</strong><br>Previously, Patchworks required APIs to return complete URLs with next page information - for example:<br><br><code>https://api.example.com/products?page=2</code><br><br>Now, relative URLs are supported. The relative URL must begin with a <code>?</code> character - for example:<br><br><code>?page=2</code><br><br>When a relative URL is returned, the base URL from the previous request is appended to the start.<br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../developer-hub/connector-builder/building-your-own-connector/4-endpoints/endpoint-options/pagination/next-page-url-pagination-method">Next page pagination URL</a></td><td>CPT-5153</td></tr></tbody></table>

## User management

<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="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="edbc33cea7f34e16b3a205c7a65c3172">New</span></td><td><p><strong>Reactivate deleted users</strong><br>It is now possible for <code>admin</code> users to reactivate a deleted user account. </p><p></p><p>When viewing users associated with your company profile, any deleted accounts are shown with a <code>restore</code> option. </p><p></p><p>Reactivated users retain their previous email, but a new password is required. As an <code>admin</code> user, you can choose to <a href="../../users-roles-and-permissions/triggering-a-password-reset-for-another-user">trigger a password reset</a> for the user, or the user can select <code>forgot your password?</code> from the dashboard login page. </p><p><br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../users-roles-and-permissions">Users, roles &#x26; permissions</a></p></td><td>CPT-4823</td></tr></tbody></table>
