Release V26.2

Requires Ignition 8.3.3 or later

Released on: 11/10/2026

Download Canary Module

Features

• Slow-changing tags are now time-extended after reconnects. When the module first connects to the Store and Forward (SAF) service, and on every reconnect after that, it sends the current value of every good-quality tag. Slow-changing tags now show up in the session right away and are time-extended as expected after a disconnect. Bad-quality tags are skipped. This works with historian splitters too. You can turn it on or off with the new Read Current Values On Startup setting in the Collector section. It is on by default for new installs and upgrades.

• One cached client connection for reads. The module now gets a single client connection ID (CCI) from Views, caches it, and reuses it for raw data, aggregate data, and annotation requests. Before, it opened a new connection for each request. This stops the module from running out of client connection IDs, cuts down on traffic, and shows one steady connection in the Views client list. Note: all Ignition users now share that one connection.

Bugs

• Datetime tags log again on Ignition 8.3. Datetime values are logged to the historian as strings, the same as on Ignition 8.1. The module also catches all exceptions during storage now, so the real error shows up in the Ignition logs instead of a generic “Error forwarding data.”
• Byte data type is supported. Tags with the Byte data type now log to the historian. Before, they failed with “Unsupported value type for Variant: class java.lang.Byte.”
• Null values are no longer skipped. When Ignition sends a null value, the module writes an empty value with bad quality. Before, it skipped the value. This makes bad-quality events show up in Canary instead of looking like gaps in the data.