v4.4.14
Integrations
Note
Although Run Recommendation v3.00 is backward compatible with App Designer, it was not compatible with Stream Host pre v4.4.2. This is rectified by Run Recommendation v3.03.
| Change Type | Name | Description |
|---|---|---|
| Feature | Meta Action Agent v1.00 | Our new Meta Agent allows you to run scripts on input values and use the results in your data stream. Similar to the Metablock, the scripts can be written in languages other than C# and leverage 3rd party libraries. |
| Enhancement | MySQL Listener v2.00 MySQL Context Provider v2.00 MySQL Action Agent v2.00 | Updated to latest NuGet package. We recommend upgrading your MySQL server to the latest version in response to medium CVE-2023-3817 security update. |
| Enhancement | Run Recommendation v3.03 | Added Rule Id to the output payload. |
| Enhancement | TSA Azure Data Explorer Connector v1.10 | Implement the new ITSAConnector interface and naming aligned to the Time Series Analysis block. |
Common
Note
Security update: Mitigate high-severity vulnerabilities by upgrading AD, AI, and DS.
| Change Type | Description |
|---|---|
| Security | Various NuGet and NPM packages upgraded for AD, AI and DS:
|
| Enhancement | We're improving our multilingual capabilities:
|
App Designer
| Change Type | Description |
|---|---|
| Fix | Several issues were corrected on the Metablock:
|
| Fix | I created a new Recommendation, but when I opened the Version blade I noticed the title was blank. The title of a new Recommendation default to "Initial Version". |
| Fix | I am the owner of a Recommendation, but I cannot view it's timeline - yet my colleague with Run Access can. Users with design access are able to view a Recommendation's timeline. |
Stream Host
| Change Type | Description |
|---|---|
| Fix | I accidentally used the incorrect password on an MQTT agent and published the data stream. The stream did not start due to the connection error on the agent, but I noticed the agent continues attempting to connect to the MQTT broker. The Stream Host ensures that if a data stream fails to start or is unpublished, all of that stream's agents (whose Create() methods have already run) are destroyed. |
Last modified: February 04, 2026