# Find References does not detect runtime properties used in Run Code via array iteration

**URL:** <https://community.appfarm.io/t/find-references-does-not-detect-runtime-properties-used-in-run-code-via-array-iteration/2489>\
**Category:** Bug reports\
**Created:** [November 2, 2026, 10:23am UTC](https://community.appfarm.io/t/find-references-does-not-detect-runtime-properties-used-in-run-code-via-array-iteration/2489 "2026-11-02T10:23:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![michael](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/michael/32/2883_2.png) [@michael](https://community.appfarm.io/u/michael)\
**Post date:** [November 2, 2026, 10:23am UTC](https://community.appfarm.io/t/find-references-does-not-detect-runtime-properties-used-in-run-code-via-array-iteration/2489/1 "2026-11-02T10:23:19Z")

</div>

Hi!

When a runtime property on a data source is used in a Run Code node through a function parameter that references the entire data source, e.g items.forEach((line) =\> line.myProperty) “Find References” on that runtime property does not show it, even though the code reads the value.

**Steps to reproduce:**

1. Create a data source with a runtime property - a function property.
2. Create a Run Code node with the entire data source as a function parameter.
3. Use the property inside a `forEach` or via index, e.g. `items[0].myProperty`.
4. Right-click the property and select Find References.

“App health” shows a warning on these, prompting the user to possibly delete assets that actually are in use.

Is this a known issue, and is there a workaround?

---

<div class="post-metadata">

**Author:** ![Eirik](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/eirik/32/76_2.png) [@Eirik](https://community.appfarm.io/u/Eirik)\
**Post date:** [November 2, 2026, 12:24pm UTC](https://community.appfarm.io/t/find-references-does-not-detect-runtime-properties-used-in-run-code-via-array-iteration/2489/2 "2026-11-02T12:24:04Z")

</div>

Thanks for the report, Michael. I’ve filed it with our development team.

One workaround (which is not ideal, but it removes the property from App Health and lets the reference check find it as well) is to add the myProperty as a function param and use it in a dummy statement in your code.

We’ll update this thread when it has been fixed.