2026-08-20

Improvements

• The Destination section of a Historian bridge now has a Visual mode next to Code. The data contract is a dropdown, the connection inherited from the instance's Historian is a single read-only row, and metadata filtering, write timeouts, compression and retention are editable fields. Compression and retention take effect only when a data contract's tables are first created. Saving from the visual form rewrites the stored YAML, so comments in it are not kept. Save & Deploy stays blocked while no data contract is selected, while the name cannot work as a Historian target, and while the destination YAML cannot be read, with the reason shown on hover.

Fixes

• Leaving a bridge that writes to the Historian no longer warns about unsaved changes when nothing was edited. Its host and port are read from the instance's Historian each time the page opens, and that counted as an edit.
• Topics and events no longer go missing from the Topic Browser when data arrives faster than it can be saved