I have a tag issue that is repeatable and manifests after a gateway restart. Our front end has some derived/ reference tags whos source is on a remote gateway tag provider.
After a restart of the front end gateway - UDT values are being updated but the qality of certain tags are not updating. In the front end UDT there are expression tags tags that reference the derived tag.
Is this caused by the tag group executing the expression before the gateway has established communication with the remote tag provider? The first expression errors in the logs indicate that there is a bad reference "Not found"
If I restart the tags they populate normally. What method might be optimal for monitoring for this condition and restarting tags automatically?
I know its been a while but this keeps intermittenly causing issues and I am looking at increasing my knowledge on best practices. Could I ask how you like to handle aggregating UDTs and data types.
We have a central gateway and remote gateways all with unique UDT definitions with alarming and history configured locally. Currently these UDT definities are directly replicated but their definitions on the primary provider just 'point' at the remote providers tags.
This is causing some confusion while troubleshooting and seems to also be duplicating history/alarming records. Any thoughts?