# \[BUG-15454\] Value of String Array tag not saving **URL:** \ **Category:** Ignition Early Access\ **Tags:** ignition80\ **Created:** [November 19, 2019, 3:24pm UTC](https://forum.inductiveautomation.com/t/bug-15454-value-of-string-array-tag-not-saving/30081 "2019-11-19T15:24:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![md.szyman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/md.szyman/32/9240_2.png) [@md.szyman](https://forum.inductiveautomation.com/u/md.szyman)\ **Post date:** [November 19, 2019, 3:24pm UTC](https://forum.inductiveautomation.com/t/bug-15454-value-of-string-array-tag-not-saving/30081/1 "2019-11-19T15:24:21Z")
So I’m currently running a Trial version of Ignition and don’t currently have a license available yet. Our company has other licenses, but we’re testing stuff out right now and there’s no license provisioned for my use at the moment, so keep that in mind I guess. I have a String Array Tag configured as in the screenshot below: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/e/e55ed52472b5bc9c897b02c080bdc179e51d4d5a.png) This tag is part of a UDT, not sure if that matters. However, the value of the tag seems to eventually just get lost. The trial just now expired and I reset it and the value was still there, but most days after checking the system again after leaving it overnight, the value has disappeared. The single event script is a tag change script that simply concatenates all the items in the array into a new string, and then writes that string to another tag. I did notice just now, however, that the tag event script was returning the concatenated string after writing it to the other tag. I’m not sure if returning from a tag event script causes problems. I don’t see anything in the documentation saying what happens to the value that a tag event script returns. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 19, 2019, 3:28pm UTC](https://forum.inductiveautomation.com/t/bug-15454-value-of-string-array-tag-not-saving/30081/2 "2019-11-19T15:28:28Z")
This is a bug that we recently became aware of. ---
**Author:** ![md.szyman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/md.szyman/32/9240_2.png) [@md.szyman](https://forum.inductiveautomation.com/u/md.szyman)\ **Post date:** [November 19, 2019, 3:29pm UTC](https://forum.inductiveautomation.com/t/bug-15454-value-of-string-array-tag-not-saving/30081/3 "2019-11-19T15:29:21Z")
Is there anything specifically that I’m doing that causes the bug? Or is it just a bug with String Array or Array tags in general? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 19, 2019, 4:04pm UTC](https://forum.inductiveautomation.com/t/bug-15454-value-of-string-array-tag-not-saving/30081/4 "2019-11-19T16:04:36Z")
The ticket says it’s just any use of String Array inside a UDT. ---
**Author:** ![md.szyman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/md.szyman/32/9240_2.png) [@md.szyman](https://forum.inductiveautomation.com/u/md.szyman)\ **Post date:** [November 19, 2019, 4:11pm UTC](https://forum.inductiveautomation.com/t/bug-15454-value-of-string-array-tag-not-saving/30081/5 "2019-11-19T16:11:50Z")
I see, thanks! ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 19, 2019, 4:25pm UTC](https://forum.inductiveautomation.com/t/bug-15454-value-of-string-array-tag-not-saving/30081/6 "2019-11-19T16:25:22Z")
We’ll update this ticket when it’s fixed. Should be relatively soon.