# Performant way to get JSON or XML from tags **URL:** \ **Category:** Ignition\ **Created:** [January 11, 2023, 11:19am UTC](https://forum.inductiveautomation.com/t/performant-way-to-get-json-or-xml-from-tags/68476 "2023-01-11T11:19:27Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [January 11, 2023, 11:55am UTC](https://forum.inductiveautomation.com/t/performant-way-to-get-json-or-xml-from-tags/68476/2 "2023-01-11T11:55:26Z")
Consider using a gateway tag change event instead. You may find this thead of interest: > [@How things work - how much code is allowed behind tag event?](https://forum.inductiveautomation.com/t/how-things-work-how-much-code-is-allowed-behind-tag-event/68443): > > My current understanding is that tag events scripting is only meant for small code like copying the value to other tag, capturing timestamp, checking logic or arithmetic operation. My understanding is that tag events errors do not show up so can go unnoticed. So from code reliability point of view: 1 - How can i know that i didn't put too much code behind tag event? Is there a way to capture an error? 2 -if there is too much code and the next tag cycle update has to happen the unfinished code … --- _[View the full topic](https://forum.inductiveautomation.com/t/performant-way-to-get-json-or-xml-from-tags/68476)._