Release R26-7 #
Available from 14th July 2026
Highlights #
Custom Connectors > Scripting – added AES encrypt/decrypt Script functions
When working with Script on Custom Connectors or on Steps, you can now encrypt and decrypt using the AES-256-GCM encryption algorithm using these 2 new functions:
Cyclr API – new GET /v1.0/accounts/usage endpoint
We’ve added a new endpoint to the Cyclr API that returns a list of your Accounts along with their Task Usage and the number of Errors and Warnings logged. You provide start and end parameters to retrieve values between 2 date/times.
Cyclr Interface – Help options now available within Accounts
When accessing Cyclr as a Console User, the same “help” options shown in the top right when you’re in your Console are now also shown when you’re within an Account.
They are not shown to Account Users within the Account User Interface. Account Users are intended for use by your customers, if you decide to provide them with access to Cyclr.
Improvements #
Connector Authentication – redaction of sensitive values
When authenticating some Connectors, providing invalid credentials could reveal values considered sensitive to the Account User/customer, such as an OAuth app’s Client Secret value. Those values are now redacted.
Console Dashboard – “Templates” no longer shown as a Recently Created Account
Newly created Cyclr Partner Consoles will no longer include an entry for “Templates” (which holds the Template Library) within their Recently Created Account section of the Dashboard.
Custom Connectors – copying a Method redirects to editing that Method
Minor change to improve the experience of working on a Custom Connector: when copying a Method, previously the interface would direct you back to the list of Methods, requiring you to locate the new Method to edit it. Now, copying a Method takes you directly to editing it.
Custom Connectors – performance improvements
When working on a Custom Connector, the speed of several operations – such as Copying or Exporting Connector Releases – has been improved.
Cycle Execution – prevent invalid Split Transactions from being executed
Identified and resolved a situation where it was possible for a Split Transaction to run that incorrectly referenced all of its parent Transaction’s data, resulting in it containing more than just its single item. Should that issue occur, Cyclr will now stop that Transaction and log a Step Error against it.
Event Triggers > Synchronous Response Steps – resolved issue with Fields
Resolved an issue where multiple Event Triggers “Synchronous Response” Steps within the same Account could impact the structure of data each returns. If one Synchronous Response defined an array of data for its Response and another defined a single object, both Synchronous Response Steps could result in returning a single object. This Release ensures each Synchronous Response Step returns the structure of data it has defined.
Quick Connector > HTTP Request Steps – corrected updating of Fields
The Quick Connector’s “HTTP Request” Steps could sometimes retain unused Fields when the JSON content on the Request/Response tab was changed. Those Fields could prevent a Template containing that “HTTP Request” Step from being installed. Correct removal of unused Fields is now performed.
Quick Connector > HTTP Request Steps – improved handling of Request/Response Fields
Improved how the Quick Connector’s “HTTP Request” Step handles JSON content provided in the Request and Response tab, for example when it includes an array of data where some objects within it have properties set as null and others contain whole objects.