# Running into issue with derived tag expression

**URL:** <https://forum.inductiveautomation.com/t/running-into-issue-with-derived-tag-expression/114146>\
**Category:** Ignition\
**Tags:** ignition83\
**Created:** [February 24, 2026, 4:52pm UTC](https://forum.inductiveautomation.com/t/running-into-issue-with-derived-tag-expression/114146 "2026-02-24T16:52:54Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 25, 2026, 11:14pm UTC](https://forum.inductiveautomation.com/t/running-into-issue-with-derived-tag-expression/114146/12 "2026-02-25T23:14:15Z")

</div>

Converting status integers from tags into corresponding strings is not a job for tags. This belongs in your user interface. See this entire topic:

> [@Slow Expression Tags](https://forum.inductiveautomation.com/t/slow-expression-tags/99527/14):
>
> Yes. Where you must use them, you should time them with java.lang.System.nanoTime() and log when \>5ms. So you can focus on removing the worst offenders. Ideally, do not run database or network operations, or make system calls that do database or network operations. Make sure the tags are in event driven mode, so they only run when a reference changes. This should not be in an expression tag at all. It will run when no one is looking at it (useless), and cannot be internationalized for mu…

In that case it is `runScript()` in expression tags, where here it is scripted lookups, but it is the same fundamental design error.

---

_[View the full topic](https://forum.inductiveautomation.com/t/running-into-issue-with-derived-tag-expression/114146)._