Quarterly Release Update for Usage Engine Cloud Edition - January 2026
During the last quarter, we have released three major features and three enhancements:
New features
Viewing and deleting tagged versions
In the last blog post, we introduced the Version history panel that allows you to tag versions on a stream, which opens up the capabilities of exporting older versions of a stream. Since then, we have expanded the capabilities of the Version history panel to view and delete tagged versions.
Previously, you had to export a tagged version of a stream and re-import it if you wanted to view an older version of the stream in the stream editor. With the new View option in the Version history panel, you can view the tagged version directly in the stream editor. Safeguards are in place to prevent you from making modifications in the tagged version so that it will not affect the latest version of the streams, and the user interface is designed to make it easy to navigate to the latest version of your stream.
To learn more about the safeguards when viewing a tagged version of a stream, see Viewing tagged versions.
A stream can have a maximum of 100 tagged versions. Until that limit is reached, you can now delete older tags before creating new ones, which prevents version sprawl and keeps the version history manageable. There are certain restrictions on deleting tagged versions to maintain the usability of scheduled streams. See Deleting tagged versions for more information.
This is another update of version tagging that will be followed by more near-term updates related to version control.
Using the Export Stream API for configuration export
The Export Stream API lets you export the full JSON configuration of any stream version for backup, migration, or audit purposes. You can export either the current version of a stream or a specific tagged version, which makes it especially useful for scripting workflows and integrating with Git. An accompanying import API is coming soon, which will make it easier to move, clone, or restore stream configurations across environments.
For a high-level introduction to Stream API capabilities, see https://infozone.atlassian.net/wiki/x/SoATNg and for links to the API documentation and guidance on how to get started, see API access guide.
Using the Lookup Aggregation API for session retrieval
With the Lookup aggregation session API, you can retrieve session details by providing the same identifying fields that your Script aggregator uses, for example, email, customer ID, or phone number. The API combines these values (in the configured order) to look up the matching session directly in the specified aggregation store.
When calling the API from an external system, you must also provide the aggregation store ID. You can find and copy this from your Script aggregator configuration page in the user interface. See the API access guide for links to API documentation and guidance on getting started.
Enhancements
Using API key authentication in HTTP client functions
API key authentication is available as a new option in HTTP client functions. This capability lets you securely connect Usage Engine Cloud Edition to a wider range of systems that use API key authentication.
Enforcing TLS connectivity for Database functions
TLS connectivity is now enforced for Database functions that connect to Oracle, MS SQL, and PostgreSQL. This enforcement encrypts all connections by default across supported databases. As a result, all connected databases must have TLS enabled.
Database functions also support Native Network Encryption for Oracle to improve protection for Oracle workloads. For details on selecting TLS and Native Network Encryption options, see: Database and Database query.
Scheduling of tagged versions
With the introduction of tagged versions, we have changed the behavior for scheduling streams since it is now possible to schedule a tagged version of a stream, instead of just the latest iteration of the stream. When you schedule a stream, you must now select a tagged version of the stream. Therefore, you must tag the version of the stream that you intend to schedule to be able to schedule it. This also applies to stream groups, where all streams in the stream group must have a tagged version before the stream group can be scheduled.
See Change notice for scheduling and execution of tagged versions for a full breakdown of the new scheduling behavior.
We hope you enjoy these new enhancements. As always, we appreciate your feedback. If you have any questions or concerns, please do not hesitate to reach out to us through our Self Service Portal.