I always had this issue with the historian. Somehow, it try to record the same tag twice.
Ignition 8.1.17 with a redundant node.
I'm about to disable the store&foward because of that.
Someone else have the same issue?
pturmel
2
Similar to this topic, except for redundancy:
I think "warm" redundancy for tag history is wonky. Might even call it buggy. The trigger option mentioned in that topic might work for you.