Release “R24-16” #
Available from 12th November 2024
Highlights #
Console > Templates > GitHub Integration – store Template Releases in your GitHub repository
It’s now possible to export Template Releases to your own GitHub repository as a way to backup them up, but also to transfer them between Cyclr Consoles. Useful for development lifecycle setups.
More on the GitHub Integration feature here
Console > Custom Connectors – Rate Limiting improvements
We’ve improved the Rate Limits that can be set on Custom Connectors and their Methods as described in the updated Rate Limits article. Existing Rate Limits aren’t affected, but you can now do more when adding new ones.
As part of these changes, Transactions held-up by a Rate Limit may be returned to the queue, no longer holding on to a Concurrent Transaction Slot in the meantime.
Cycle Execution – improvement to CSV content handling
When working with CSV content, Cyclr converts it into JSON to be able to process it line-by-line. When storing that data as part of a Transaction, the JSON version of the data would be stored, which is much larger than the original CSV content. That could more easily result in the 100 MB/Transaction/Step limit being reached.
This change causes the original CSV content to be stored, allowing an increase to the size of data that can be processed.
Improvements #
Console > Templates – corrected issue setting Variables using “2-level Lookups”
Previously, if you were to create a Template Variable and assign it to a “Sheet Name” field of perhaps a Google Sheets Step, when attempting to use the 2 Lookups to first select a Spreadsheet and then select the Sheet, the second Lookup for the Sheet Name would fail.
Cyclr API > Calling Connector Methods – errors now returned as JSON objects
When using the Cyclr API to call Connector Methods directly, if the remote system returns an error, Cyclr’s API will now return a JSON object in its Response. Previously it returned an unformatted string representing the error.
Marketplaces – clicking Integration Package “Details” option sometimes just reloaded the page
Resolved an issue that might occur which caused clicking the “Details” option of an Integration Package to just reload the page, rather than taking the user to see the Cycles that had been created.
Cycle Execution – try/catch blocks in Script can catch errors when invalid URL used in http_request() call
When using the http_request() Script function in either a Custom Connector or Step-level Script, if an invalid URL was passed to it, Cyclr would catch the error itself and stop running the rest of that Script function. Now, Cyclr won’t catch that itself, but will continue executing Script, allowing you to try/catch it to handle yourself.
