Unfortunately I have no idea why this is happening. Can anyone provide any insight?
Regular queries in the query browser execute fine.
I would look for something else in that tag group not completing, preventing other tags from executing. Consider moving that tag to its own tag group with the same settings and see if it then executes.
Thanks. I am running it “Fixed Rate”. I thought that bypassed the tag group. But, I did make an entirely new tag group and it still starts up with the uncertain initial value. It will eventually update, minutes later. If I execute the query in the query browser it executed in way less than a second.
Something is hogging your tag subsystem’s thread pool. You’ll have to poke around to find it. (I often find scripts with some form of sleep in them when looking at such things for clients.) Also consider moving your query to a gateway timer script.
Thank you for bailing me out. This is why I love these forums. I will dig into that. For now, moving the query to a gateway event timer script worked. Is there a reason why that is a preferred best practice rather than doing the query on a tag?
- Gateway project scope instead of gateway global scope.
- Option for a dedicated thread.
- Single event script can run multiple queries in any desired order, writing results to memory tags with any desired timing.
- Event scripts can post-process results before writing to tags, relieving the DB of static joins and other lookups. Including using cached lookups.
- Event scripts can drive multiple target tags from single, larger queries.
- Event scripts can simulate joins across datasources.
- Easy parallelism control with separate event scripts.
- Even when not using a dedicated thread, gateway events use a different thread pool than tag groups and tag events.
9) Tag groups (and v7.9 scan classes) are operationally opaque–very un-fun to troubleshoot.
Okay I have got that problem resolved. I did find an instance of the “wait” command, but thats resolved. I really don’t want to have to recreate all of these query tags if I don’t have to. Is there someone on the Ignition team that may be able to help me narrow in on what is causing the problem?
Raise a ticket with support. This forum isn’t an official support channel.
Done. Thanks. It has been a while since I had to reach out.