# User Management - Email Not Loading During Debugging

**URL:** <https://sygnal-attr.discourse.group/t/user-management-email-not-loading-during-debugging/201>\
**Category:** Support\
**Created:** [June 27, 2024, 4:54am UTC](https://sygnal-attr.discourse.group/t/user-management-email-not-loading-during-debugging/201 "2024-06-27T04:54:22Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![emmanuel128](https://avatars.discourse-cdn.com/v4/letter/e/ecc23a/32.png) [@emmanuel128](https://sygnal-attr.discourse.group/u/emmanuel128)\
**Post date:** [June 27, 2024, 4:54am UTC](https://sygnal-attr.discourse.group/t/user-management-email-not-loading-during-debugging/201/1 "2024-06-27T04:54:22Z")

</div>

Hi everyone,

I’m reaching out regarding an issue we’re encountering in our Webflow project related to user management. Our project utilizes multiple access groups (students, admins, and tutors) and leverages the `getMembershipConfig` and `userInfoChanged` functions within the site’s custom code. This setup successfully retrieves user information and redirects users to the appropriate page based on their access group.

While the functionality generally works well, we’ve encountered an issue during debugging with multiple accounts. Specifically, user information, such as email, stops loading.

Here’s my question:

- Is this a recognized issue with `userInfoChanged`?
- Are there any known workarounds to prevent this behavior?
- Alternatively, are there other recommended methods to access the logged-in user’s email address within Webflow’s custom code?

Site custom head code implementation:

```auto
window.sa5.push(['userInfoChanged', 
    (user) => {
      // debugger;
      currentUser = user; // saving into a variable to access across pages
      console.log("USER INFO CHANGED", user);
      
      let newUrl = window.location.origin;  
      switch(user.access_groups[0]){
      // redirect logic
      }
}]);

```

Tutor page before implementation:

```auto
window.sa5.push(['userInfoChanged', 
                   (user) => {
                     //currentUser = user;
                     console.log("USER INFO TUTOR", user);
                   }]);

```

Here is the [read only URL](https://preview.webflow.com/preview/aprende-conmigo-cdn?utm_medium=preview_link&utm_source=designer&utm_content=aprende-conmigo-cdn&preview=e36692f4fd95cf8460b8e385555ccd90&workflow=preview)

Example of the returned user object:

 ![image](https://global.discourse-cdn.com/free1/uploads/sygnal_attr/original/1X/4d14ffef4357c11a4a587795da49cbe671203e57.png)

---

<div class="post-metadata">

**Author:** ![memetican](https://yyz2.discourse-cdn.com/free1/user_avatar/sygnal-attr.discourse.group/memetican/32/9_2.png) [@memetican](https://sygnal-attr.discourse.group/u/memetican)\
**Post date:** [June 27, 2024, 8:22pm UTC](https://sygnal-attr.discourse.group/t/user-management-email-not-loading-during-debugging/201/2 "2024-06-27T20:22:30Z")

</div>

Make certain you’re using the latest version of the library, I’ve made some changes lately to support unusual network caching configs.

Otherwise, no. SA5 watches the entire process- log in, use the website, change info on the user accounts page, log out, and should always know your state. If you’re logging in and logging out as different users, should still work fine.

Note that Webflow will block logins at some point if you login/logout too many times from the same IP.

---

<div class="post-metadata">

**Author:** ![emmanuel128](https://avatars.discourse-cdn.com/v4/letter/e/ecc23a/32.png) [@emmanuel128](https://sygnal-attr.discourse.group/u/emmanuel128)\
**Post date:** [June 28, 2024, 2:51am UTC](https://sygnal-attr.discourse.group/t/user-management-email-not-loading-during-debugging/201/3 "2024-06-28T02:51:33Z")

</div>

Thanks for the response! I actually just updated to Webflow version 5.4.0, hoping that might resolve the issue. Unfortunately, I’m still encountering the incomplete user object after successfully logging in with two different accounts.

However, I can log in/log out with different accounts without any problems, but the user object, stops loading some data like the email.

Can you elaborate or post more information about Webflow blocking logins?

Example of the line of code used:

```auto
<script defer src="https://cdn.jsdelivr.net/gh/sygnaltech/webflow-util@5.4.0/dist/nocode/webflow-membership.js"></script>

```

---

<div class="post-metadata">

**Author:** ![memetican](https://yyz2.discourse-cdn.com/free1/user_avatar/sygnal-attr.discourse.group/memetican/32/9_2.png) [@memetican](https://sygnal-attr.discourse.group/u/memetican)\
**Post date:** [June 28, 2024, 5:01am UTC](https://sygnal-attr.discourse.group/t/user-management-email-not-loading-during-debugging/201/4 "2024-06-28T05:01:58Z")

</div>

Best guess would be a network issue or a server-side issue that’s causing a delay.  
In the client-side SA5 libs, we have to pull the data from the /user-account page, and there’s an unknown delay before webflow.js makes that information accessible in the fields.

I’ve never encountered any issues like what you’re describing, but that’s the most likely scenario in which the info would not be available.

However the email address, for example, is captured at login, and is not re-retrieved. If your browser has extremely low memory, it may shut down webStorage, or affect your cache abilities, which would basically give it amnesia about what’s happening on the site.

You’d just need to dig through the situation using devtools to identify when and how the data is disappearing.

I primarily do client builds using our server-side products because the retrieval is instantaneous and more comprehensive ( it includes User ID ), and I can do things access-group gating on elements.

But many of my sites still use the client-side libs and we’ve not observed any issues or changes on Webflow’s end.

---

<div class="post-metadata">

**Author:** ![fngrz](https://avatars.discourse-cdn.com/v4/letter/f/bc8723/32.png) [@fngrz](https://sygnal-attr.discourse.group/u/fngrz)\
**Post date:** [July 22, 2024, 6:54pm UTC](https://sygnal-attr.discourse.group/t/user-management-email-not-loading-during-debugging/201/5 "2024-07-22T18:54:39Z")

</div>

I’ve experienced this with 5.4.0. It’s inconsistent — sometimes it loads and sometimes it doesn’t. Unclear why.

---

<div class="post-metadata">

**Author:** ![memetican](https://yyz2.discourse-cdn.com/free1/user_avatar/sygnal-attr.discourse.group/memetican/32/9_2.png) [@memetican](https://sygnal-attr.discourse.group/u/memetican)\
**Post date:** [July 23, 2024, 5:30am UTC](https://sygnal-attr.discourse.group/t/user-management-email-not-loading-during-debugging/201/6 "2024-07-23T05:30:02Z")

</div>

Thanks @fngrz that’s good to know.

Based on your description I am suspicious that Webflow’s servers may have slowed a bit on the /user-account data loading, or perhaps you’re experiencing a network delay- I’m unable to reproduce it.

I’ve added some documentation under the troubleshooting page that includes an advanced setting that defines the amount of time SA5 wait for Webflow to load its data. Normally this is 300ms for loading the /user-account page data, or 500ms when the user makes a change and saves the data.

That’s always been configurable but I’ve just realized it’s not in the docs, so most people who use it know about it only from the Git repo code directly.

> **[Troubleshooting | Sygnal Attributes | Designed for Webflow](https://attr.sygnal.com/sa5-user-accounts/logged-in-user-info/troubleshooting#user-data-usually-loads-but-sometimes-it-doesnt)**
>
> Troubleshooting and FAQs for SA5's Current User Info.

@emmanuel128 you should try this as well.