# \[BUG\_5647\] Tag Browser - Values flash from visible to blank for a few seconds when expanded

**URL:** <https://forum.inductiveautomation.com/t/bug-5647-tag-browser-values-flash-from-visible-to-blank-for-a-few-seconds-when-expanded/56655>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [March 1, 2022, 2:32am UTC](https://forum.inductiveautomation.com/t/bug-5647-tag-browser-values-flash-from-visible-to-blank-for-a-few-seconds-when-expanded/56655 "2022-03-01T02:32:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [March 1, 2022, 2:32am UTC](https://forum.inductiveautomation.com/t/bug-5647-tag-browser-values-flash-from-visible-to-blank-for-a-few-seconds-when-expanded/56655/1 "2022-03-01T02:32:13Z")

</div>

v8.1.5

When expanding a folder/UDT instance, tag values are shown briefly and then they all disappear for a few seconds before coming back again. This is particularly annoying for UDT parameters which I just want to quickly skim over to check for correct values. Sometimes they can take a good few seconds to come back again. My question is: can these stay there and not go blank?

[https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/4/e4b363b80357177b531b19d3324d69d54dd90d76.mp4](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/4/e4b363b80357177b531b19d3324d69d54dd90d76.mp4)

---

<div class="post-metadata">

**Author:** ![CosmoStevens](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cosmostevens/32/32309_2.png) [@CosmoStevens](https://forum.inductiveautomation.com/u/CosmoStevens)\
**Post date:** [March 2, 2022, 5:01pm UTC](https://forum.inductiveautomation.com/t/bug-5647-tag-browser-values-flash-from-visible-to-blank-for-a-few-seconds-when-expanded/56655/2 "2022-03-02T17:01:34Z")

</div>

Thanks for bringing this to our attention. I filed a bug ticket and the Devs are looking into it.
