# Forms Router Exists bug

**URL:** <https://community.auth0.com/t/forms-router-exists-bug/200545>\
**Category:** Get Help\
**Tags:** users, management-api\
**Created:** [June 5, 2026, 4:35am UTC](https://community.auth0.com/t/forms-router-exists-bug/200545 "2026-06-05T04:35:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jarren.ong](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jarren.ong/32/71057_2.png) [@jarren.ong](https://community.auth0.com/u/jarren.ong)\
**Post date:** [June 5, 2026, 4:35am UTC](https://community.auth0.com/t/forms-router-exists-bug/200545/1 "2026-06-05T04:35:31Z")

</div>

When using a Form Router to check `{{context.user.app_metadata.status}}`, with the `user.app_metadata` set as the default `{ }`, “exists” incorrectly returns true.

When using “has value”, this correctly returns false.

 ![image](https://global.discourse-cdn.com/auth0/original/3X/d/4/d4ef9092b14223004a1deb084a0802d685ef346c.png)

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [June 5, 2026, 6:54pm UTC](https://community.auth0.com/t/forms-router-exists-bug/200545/3 "2026-06-05T18:54:32Z")

</div>

Hi @jarren.ong

The **has value** is the right operator to use when checking for the presence of data inside `app_metadata` .

The “exists” operator is returning `true` because it is performing a structural definition check, rather than a strict data check. Because the parent object (`app_metadata` ) is explicitly initialized as an empty object `{}` , the router considers the object path to “exist,” even if the specific leaf property (`status` ) is undefined.

→ When the router evaluates `{{context.user.app_metadata.status}}` using “exists”, it checks if the reference is structurally valid within the context. Because Auth0 initializes `app_metadata` as `{}` by default, the `app_metadata` object technically exists. The engine sees that the parent object is present and, rather than throwing an undefined error for `status` , it loosely evaluates the path’s existence as `true` .

→ When you switch to “has value”, the router performs a much stricter evaluation on the final leaf node (`status` ). It checks if the actual result of the expression is populated (i.e., not `undefined` , not `null` , and not an empty string `""` ). Because `status` does not have a value inside the `{}` object, it correctly returns `false` .

When evaluating nested JSON properties like `app_metadata` or `user_metadata` in Auth0 Forms, you should default to using **“has value”** to determine if a property has been populated.

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![jarren.ong](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jarren.ong/32/71057_2.png) [@jarren.ong](https://community.auth0.com/u/jarren.ong)\
**Post date:** [June 10, 2026, 12:54am UTC](https://community.auth0.com/t/forms-router-exists-bug/200545/4 "2026-06-10T00:54:43Z")

</div>

Hi Nik,

I understand but if that’s the case maybe the “exists” operator should be updated to check for the nested property or object. I can see other users potentially expecting the same result as me and objectively, the `status` property does not exist in this scenario.

ie how does this make sense for an operator named “exists”

> Because the parent object (`app_metadata` ) is explicitly initialized as an empty object `{}` , the router considers the object path to “exist,” even if the specific leaf property (`status` ) is undefined

Warm regards,

Jarren

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [June 24, 2026, 12:54am UTC](https://community.auth0.com/t/forms-router-exists-bug/200545/5 "2026-06-24T00:54:55Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
