# Bug: Wrong app\_metadata record updated in a multi-tenant architecture

**URL:** <https://community.auth0.com/t/bug-wrong-app-metadata-record-updated-in-a-multi-tenant-architecture/135126>\
**Category:** Get Help\
**Tags:** user-password-management, user-management\
**Created:** [May 28, 2024, 2:14pm UTC](https://community.auth0.com/t/bug-wrong-app-metadata-record-updated-in-a-multi-tenant-architecture/135126 "2024-05-28T14:14:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![marcelina.barycka](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/marcelina.barycka/32/56162_2.png) [@marcelina.barycka](https://community.auth0.com/u/marcelina.barycka)\
**Post date:** [May 29, 2024, 12:52pm UTC](https://community.auth0.com/t/bug-wrong-app-metadata-record-updated-in-a-multi-tenant-architecture/135126/2 "2024-05-29T12:52:21Z")

</div>

Hi there @nrzayeva ,

> [@nrzayeva](#):
>
> From testing, it seems like `app_metadata` is always getting read from second level tenant while the updates happen on first level tenant.

My understanding is as follows:

If tenant2 serves as an Identity Provider in this configuration, users’ profile data from IdP will be synced to Tenant1 records. (Just like when users log into your application via a social Identity Provider like Google, selected Google user profile fields will be synced with the Auth0 tenant.)

Thus, to update the app\_metadata in tenant2, my idea would be to call the tenant2’s Management API within the Action script hosted in the tenant1, similar as mentioned here: [Update App Meta Data from Post User Registration - #6 by stephanie.chamblee](https://community.auth0.com/t/update-app-meta-data-from-post-user-registration/62720/6)

What do you think?

---

_[View the full topic](https://community.auth0.com/t/bug-wrong-app-metadata-record-updated-in-a-multi-tenant-architecture/135126)._
