2026 01 21 release notes (core)

Release summary

This page summarises items scheduled for the following release to the Patchworks Core Production environment.

Release version	Release date
v2026-01-21	Wednesday 21st January 2026 (a.m)

This release is currently in testing - the items detailed below (together with associated documentation) are subject to change. Please check back on release day for final updates.

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

• ​Connectors & instances

• Process flows

• Blueprints

• Virtual environments

• Connector builder

Connectors & instances

Type	Summary	Ref #
Enhancement	Test instance authentication before saving 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. In this release, a test instance connection button has been added, so you can verify credentials before saving changes. Updating a connector instance	CPT-4778

Process flows

Type	Summary	Ref #
New	Support for HMAC signatures in webhooks HMAC (Hashed Message Authentication Code) signatures are now supported for additional security in webhooks. Using HMAC-verified webhooks	CPT-732
Enhancement	Visibility of deleted flow versions in run logs 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 deleted tag. If you choose to view detailed logs for this run, you will see the following text noted for the flow version: Flow version has been permanently deleted. Working with run logs	CPT-5098
Enhancement	Tracked data enhancements This release includes performance improvements for retrieving tracked data. As part of this, historic tracked data is being migrated to a new framework. 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. Other key improvements are: The tracked data page has been completely redesigned for easier use and improved efficiency. Tracked data is now available immediately (previously, data was updated every ten minutes). Documentation in progress	CPT-4872
Change	Try/catch shape retries Typical behaviour for process flow shapes is to retry automatically in the event of a shape failure. However, when the try/catch shape was introduced, shape-specific retries were ignored for shapes in a try/catch path. 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. The try/catch shape	CPT-3885
Bug	Status colour for retried flow runs in run logs Fixed an issue where the status associated with retried flow runs was not displayed in the correct colour. Now: If a failed run is retried and is still running, the original retried status is shown in blue. If a failed run is retried and the retry is successful, the original retried status is shown in green. If a failed run is retried and the retry fails, the original retried status is shown in red. Retrying a failed process flow run	CPT-4999
Bug	Using variables in route shape filters Fixed an issue where references to flow and environment variables in route filters were not working as expected. Now, these variable types can be defined in filters as a key, as a value, or both. The route shape	CPT-5010
Bug	Erroneous try/catch behaviour Fixed an issue where a failed step before a try/catch shape could trigger the catch path despite the try path not executing. The try/catch shape	CPT-3777

Blueprints

Type	Summary	Ref #
Bug	Branch shape sequencing in process flows Fixed an issue where branch shape paths in process flows may be incorrectly sequenced in process flows installed via a blueprint. Blueprints	CPT-5104

Virtual environments

Type	Summary	Ref #
Enhancement	Deployments page improvements Filters on the deployments page have been updated to ensure: All virtual environments with at least one flow deployment are available for selection. All packages with at least one deployment are available for selection. Additionally: Flow, package and virtual environment names are now displayed as hyperlinks for easy navigation. 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). Viewing current flow deployments	CPT-4928

Connector builder

Type	Summary	Ref #
Bug	Script pagination Fixed an issue where referencing $payload['request']['body'] in a pagination script failed to pass in body content from the latest request. Pagination scripts	CPT-5003