# Possible bug with Query Tags and implicit .value in Ignition 8.3.1 **URL:** \ **Category:** Ignition\ **Created:** [March 4, 2026, 3:20pm UTC](https://forum.inductiveautomation.com/t/possible-bug-with-query-tags-and-implicit-value-in-ignition-8-3-1/114316 "2026-03-04T15:20:49Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![gregory.bernard1](https://avatars.discourse-cdn.com/v4/letter/g/cab0a1/32.png) [@gregory.bernard1](https://forum.inductiveautomation.com/u/gregory.bernard1)\ **Post date:** [March 4, 2026, 3:20pm UTC](https://forum.inductiveautomation.com/t/possible-bug-with-query-tags-and-implicit-value-in-ignition-8-3-1/114316/1 "2026-03-04T15:20:49Z")
Hello, I might be encountering a bug with Query Tags in Ignition 8.3.1. In our projects, we use UDTs across multiple plants, and inside these UDTs we have several simple Query Tags that read configuration parameters stored in a database. This approach works correctly on most of our plants and most UDT instances. However, in some rare cases (like the example below), the Query Tag returns **null** , even though the query should return a valid value. For example, here I am simply reading a parameter for a specific LineID: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/a/2a6053bbcdf6c334829e42ced3c08b6d9332dab5.png) As shown in the screenshot, the Query Tag returns **null** , but if I execute the exact same query directly in the database, it correctly returns the expected value. After investigating, I found that if I modify the query to explicitly reference the tag value ({…LineID.value} and not {…LineID}): ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/5/b56cf2a141864036dc379e12f84d350089f3262a.png) then the Query Tag immediately returns the correct result. For now I will probably add **.value** everywhere to avoid the issue, but I find this behavior surprising because: - This happens only on a few UDT instances out of ~30 - Other instances using the exact same query work correctly - It appears on one gateway running 8.3.1 - The **lineID** tag itself has Good quality and the correct value My understanding was that when referencing a tag without specifying a property, Ignition implicitly uses **.value** , so both syntaxes should behave the same. So my question is: - Is this a known issue or regression in 8.3.x? - Or is it considered best practice to explicitly use `.value` in Query Tags? Thanks! ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [March 4, 2026, 3:50pm UTC](https://forum.inductiveautomation.com/t/possible-bug-with-query-tags-and-implicit-value-in-ignition-8-3-1/114316/2 "2026-03-04T15:50:17Z")
> [@gregory.bernard1](#): > > {…LineID} Have you tried putting the refrence in quotes? ` "{…LineID}"` ---
**Author:** ![gregory.bernard1](https://avatars.discourse-cdn.com/v4/letter/g/cab0a1/32.png) [@gregory.bernard1](https://forum.inductiveautomation.com/u/gregory.bernard1)\ **Post date:** [March 4, 2026, 4:25pm UTC](https://forum.inductiveautomation.com/t/possible-bug-with-query-tags-and-implicit-value-in-ignition-8-3-1/114316/3 "2026-03-04T16:25:20Z")
Yes, I tested it just in case, but the tag returns an error with the quotes. LineID is an int. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 4, 2026, 4:55pm UTC](https://forum.inductiveautomation.com/t/possible-bug-with-query-tags-and-implicit-value-in-ignition-8-3-1/114316/4 "2026-03-04T16:55:07Z")
> [@gregory.bernard1](#): > > Is this a known issue or regression in 8.3.x? I don't see anything that exactly lines up with this, but I would encourage updating to 8.3.4 once it's available ~~(should be as soon as this week)~~ it's now available. If you're still having issues after that, I'd say to contact support. Your expectation that `.value` should work (and consistently) is totally valid. ---
**Author:** ![gregory.bernard1](https://avatars.discourse-cdn.com/v4/letter/g/cab0a1/32.png) [@gregory.bernard1](https://forum.inductiveautomation.com/u/gregory.bernard1)\ **Post date:** [March 5, 2026, 2:14pm UTC](https://forum.inductiveautomation.com/t/possible-bug-with-query-tags-and-implicit-value-in-ignition-8-3-1/114316/5 "2026-03-05T14:14:53Z")
Thanks for the answer. We will install the new version and test. However, I would like to add another feedback. Today I encountered a similar issue on another one of our gateways running **8.3.3**. In a Perspective page, I have several custom properties. One of them constantly returns 0, but only for one specific UDT instance. This happens whether the property is bound through an expression binding: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/7/97776ff5b25a1a0e0ad70362a203a0bee4471dee.png) or through a direct tag binding: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/c/dcaee2f362d426df49b70fe76757c1922d3379ca.png) As shown in the screenshots, the displayed result is always 0, while the actual tag value is 10. Again, the only way to get the correct value is to explicitly reference .value. Once **.value** is added, the correct value is returned. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/5/a57b58d4d675d17ba667a06db73599b9b901faf5.png) Adding **.value** itself is not a problem. The main issue is that it would require us to modify all of our Ignition projects for this newer version. At first glance everything seems to work correctly, but in some specific UDT instances this bug appears, which ends up creating unexpected and confusing behaviors for users in the application. So it is difficult for us to reliably detect where this issue might occur, **but as soon as I click on “Restart tags” in the designer in the folder that is causing the problem, the error disappears.** ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 5, 2026, 4:25pm UTC](https://forum.inductiveautomation.com/t/possible-bug-with-query-tags-and-implicit-value-in-ignition-8-3-1/114316/6 "2026-03-05T16:25:43Z")
I'd definitely contact support at this point. It seems like there might be something going on within the tag execution system that's manifesting as these symptoms in two different areas.