With a tag history splitter configuration using two database sources - is there a known behavior that, for select tagpaths, Ignition may retire+create a new tag ID in one data source, but not the other?
I'm finding Ignition will retire tag ID's for certain tagpaths in our secondary data store, SCADA_History.sqlth_te, but will leave the original tagpath in the primary data store, SCADA.sqlth_te. This increments the tag id only in the secondary data store, so all newly created tags will have offset IDs between the two.