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, and see it coming into Canary:
"Sandbox.RenameTest.Temperature"
I rename the tag in Ignition to "Sandbox.RenameTest2.Temperature"
.
I then attempt to rename it in Canary to:
"Sandbox.RenameTest.Test"
However, I got the following error:
Error changing "Sandbox.RenameTest.Temperature" to "Sandbox.RenameTest.Test": Tag is currently being accessed or logged.
The strange part is that "Sandbox.RenameTest.Temperature" is no longer being logged in Ignition. I verified this in the Canary Admin, and I don’t see any new data coming in for this tag.
Additional Attempt & Error
Since renaming failed, I tried marking "Sandbox.RenameTest.Temperature"
as obsolete, but I got another error:
"Tag is currently logging."
Questions
- Can you only obsolete/rename tags from the previous day?
- How can I force a rename or mark the tag as obsolete?
- Are there any known workarounds for this issue in CanaryLabs?
Has anyone encountered something similar? Any help would be greatly appreciated!
Thanks in advance!
2 replies
-
Right, a colleague just reminded me I had to shut down the receiver when renaming in today's file.
Well, the next issue I still have then is "Sandbox.RenameTest.Temperature", still reappears, even though it was removed in Ignition and renamed in Canary. So there is no more data in the tag, but it still reappears in Canary as a tag. Why is that and how to avoid it? -
Hi ,
A tag cannot be renamed or obsoleted if it is being logged to or read from. In your case, even though the tag wasn't being actively logged to anymore, the tag itself would've still had a writer on it coming from the module.
When the module picks up a tag to log from Ignition, that tag remains in the logging session until the module is restarted or the session is disabled/enabled, even if the tag has been removed/renamed in Ignition. There is no mechanism to automatically drop the tag out of the logging session. Restarting the module or disabling/enabling the Canary Collector will force the module to create a new logging session which will only contain the current tags that are being historized in Ignition. When that happens, you'll be able to rename or obsolete old tags in Canary.