We recently set up a gateway network between 2 gateways -- one of them is a brand new installation of Ignition, the other was an existing one with lots of tags and event scripts, etc.
We set up a remote tag provider on the new gateway so we could see the tags on the old gateway.
We changed the service security settings on the old gateway such that tag access is read/write:
After this, we started seeing the behavior of the tags occurring on each gateway, i.e. duplicated. For example, a tag that is meant to trigger a label print would fire twice, and 2 labels would be printed.
We need to be able to write to tags from the new gateway, but we don't want the duplicated scripting behavior. Can anyone offer guidance on the best way to go about this migration? We have been following the scale out guide provided by Inductive Automation:
That's not how remote tag providers work. The only gateway actually executing internal logic to the tags, such as value changed scripts, is the 'source' gateway. Remote gateways don't run those tag event scripts (though duplicated projects could be running the same tag change scripts).
Are you sure someone didn't restore a gateway backup somewhere else in the network, or create a duplicate tag provider, or something else like that, independent of the gateway network stuff?
That's what I thought -- and after further investigation it does seem like it was caused by something unrelated, with unfortunate timing... I really appreciate the response.