Hello everyone,
I’m looking for some technical advice regarding the management of several Query Tags configured within a UDT.
Currently, these tags operate with a rather long Fixed Rate (5-10 minutes) but I run into a critical issue every time the server is restarted. In these instances, the data is only updated once the first scan interval is reached, forcing me to wait a long time before seeing the actual values in the system.
I was wondering if there is a native way to force these queries to update at Gateway boot, or if it’s unavoidable to implement a custom solution to bypass the wait for the first refresh cycle.
Thank you
Query tags should be minimized where possible, in my opinion. That aside, I would assume they would run immediately on boot up. I cannot understand why it would wait for the end of a polling cycle.
If they really do not poll on boot, you could turn them into dataset memory tags and use a script to populate the tags as needed.
You could also create a custom tag group and use system.tag.requestGroupExecution() to force polling as necessary.
1 Like
Wondering if they're running on boot, but the DB connection isn't yet alive...
Yeah, I thought about that too, but you would think that the boot up sequence would be such that DB connections are brought up before tags and other possibly DB dependent items.