# 2026 01 21 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-01-21     | Wednesday 21st January 2026 (a.m) |

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

* ​[Connectors & instances](#process-flows)
* [Process flows](#process-flows-1)
* [Blueprints](#blueprints)
* [Virtual environments](#virtual-environments)
* [Connector builder](#connector-builder)

## Connectors & instances  <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="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Test instance authentication before saving</strong><br>Previously, updating and then saving authentication details for a connector instance checked if the given credentials were valid - if yes, the instance was saved, and if no, an error was given. <br><br>In this release, a <code>test instance connection</code> button has been added, so you can verify credentials before saving changes. <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="../../connectors-and-instances/working-with-instances/updating-an-instance">Updating a connector instance</a></td><td>CPT-4778</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="edbc33cea7f34e16b3a205c7a65c3172">New</span></td><td><p><strong>Support for HMAC signatures in webhooks</strong> <br><em>HMAC (Hashed Message Authentication Code)</em> signatures are now supported for additional security in webhooks.</p><p><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/trigger-shape/trigger-shape-webhook/using-hmac-verified-webhooks">Using HMAC-verified webhooks</a></p></td><td>CPT-732</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Visibility of deleted flow versions in run logs</strong><br>When viewing run logs, it's now easier to see if the flow version associated with a run has been deleted. In the run logs list, the process flow name/version is appended with a <code>deleted</code> tag. If you choose to view detailed logs for this run, you will see the following text noted for the flow version: <code>Flow version has been permanently deleted</code>.<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/error-reporting-and-exception-handling/run-logs-and-queue/working-with-run-logs">Working with run logs</a></td><td>CPT-5098</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><p><strong>Tracked data enhancements</strong><br>This release includes performance improvements for retrieving tracked data. As part of this, historic tracked data is being migrated to a new framework. </p><p></p><p>Your latest data will be available soon after the release, and we anticipate that all data older than 2 days will be accessible within 24 hours of this release.</p><p></p><p>Other key improvements are:<br></p><ul><li>The <code>tracked data</code> page has been completely redesigned for easier use and improved efficiency.</li><li>Tracked data is now available immediately (previously, data was updated every ten minutes).</li></ul><p><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/track-data-shape/the-tracked-data-page">Tracked data</a></p></td><td>CPT-4872</td></tr><tr><td><span data-option="d8457d8925c74fab90fa132d141b764b">Change</span></td><td><p><strong>Try/catch shape retries</strong><br>Typical behaviour for process flow shapes is to retry automatically in the event of a shape failure. However, when the <code>try/catch</code> shape was introduced, shape-specific retries were ignored for shapes in a try/catch path. <br><br>In this release, shape-specific retries are introduced. Now, if a shape fails, its automatic retries must be exhausted before the try/catch is executed.</p><p><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">The try/catch shape</a></p></td><td>CPT-3885</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><p><strong>Status colour for retried flow runs in run logs</strong><br>Fixed an issue where the status associated with retried flow runs was not displayed in the correct colour. Now:</p><ul><li>If a failed run is retried and is still running, the original retried status is shown in <mark style="background-color:blue;">blue</mark>.</li><li>If a failed run is retried and the retry is successful, the original retried status is shown in <mark style="background-color:green;">green</mark>.</li><li>If a failed run is retried and the retry fails, the original retried status is shown in <mark style="background-color:red;">red</mark>.</li></ul><p><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/error-reporting-and-exception-handling/run-logs-and-queue/working-with-run-logs/handling-failed-process-flow-runs/retrying-a-failed-process-flow-run">Retrying a failed process flow run</a></p></td><td>CPT-4999</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Using variables in route shape filters</strong><br>Fixed an issue where references to <code>flow</code> and  <code>environment</code> variables in route filters were not working as expected. Now, these variable types can be defined in filters as a <code>key</code>, as a <code>value</code>, or both.<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/route-shape">The route shape</a></td><td>CPT-5010</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Erroneous try/catch behaviour</strong><br>Fixed an issue where a failed step <em>before</em> a <code>try/catch</code> shape could trigger the <code>catch</code> path despite the <code>try</code> path not executing.<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">The try/catch shape</a></td><td>CPT-3777</td></tr></tbody></table>

## Blueprints

<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>Branch shape sequencing in process flows</strong> <br>Fixed an issue where branch shape paths in process flows may be incorrectly sequenced in process flows installed via a blueprint. <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="../../blueprints/blueprints-introduction">Blueprints</a></td><td>CPT-5104</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>Deployments page improvements</strong><br>Filters on the deployments page have been updated to ensure:</p><ul><li>All virtual environments with at least one flow deployment are available for selection.</li><li>All packages with at least one deployment are available for selection.</li></ul><p>Additionally:</p><ul><li>Flow, package and virtual environment names are now displayed as hyperlinks for easy navigation.</li><li>If the flow version associated with a deployment has subsequently been deleted, you will see a deleted marker against the flow name (the deployment entry remains in place for reference).</li></ul><p><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-4928</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="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><p><strong>Script pagination</strong><br>Fixed an issue where referencing </p><p><code>$payload['request']['body']</code> in a pagination script failed to pass in body content from the latest request. <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/custom-scripting/pagination-scripts">Pagination scripts</a></p></td><td>CPT-5003</td></tr></tbody></table>