-
Bug: Tag Leakage between Ignition Canary Collectors
In Ignition, whether you delete a single tag with its historical storage provider explicitly assigned, or a UDT instance with its tags' historical storage providers assigned through a parameter…
-
Module Returns Incorrect LastValue Aggregate Results to Ignition
The following are inaccuracies observed when using Ignition's (v. 8.1.36) LastValue aggregate with its system.tag.queryTagHistory() function, in conjunction with the Canary Historian (v. 22.3.0.…
-
Issue with Renaming a Tag in Canary using Ignition module: "Tag is Currently Being Accessed or Logged"
Context I’m working with data flowing from Ignition → CanaryLabs. Recently, I encountered an issue while trying to rename a tag in Canary. Problem I create a tag in Ignition,…
-
Ignition Module does not like periods in tag provider name
Greetings! I can't find this explicitly stated in the documentation, but are periods permitted when naming tag providers in Ignition? My lucky permutation is as follows: * Ignition 8.1.…
-
Deleting Collectors Doesn't Work
When a Canary Collector is deleted, the version 23.0.0 Canary Historian Module does not delete/unregister the store and forward sink associated with the Canary Collector.…
-
No option for "includeBounds" in Ignition module.
Hi, I am using the Ignition module, but there does not appear to be any option to "includeBounds" as there is in the web API (see the above images). Neither setting "includeBoundingValues" to True,…
- Fixed
Help us improve by reporting issues, bugs or enhancement requests.