Current plan level (Business)
Version of Retool (if self-hosted):
Question / Description:
Hi, we are using retool external apps and onboarding external users. We are relying on user attributes to identify some of them but we've noticed an error where despite adding the attributes, clicking on the tick mark, and creating the user, the attribute disappears after a while when we come back to double check
This experience is poor and we were able to replicate this issue a few times. Do let us know if this is a known issue that is currently worked on and to what extent it may disappear.
Hi folks, we recently patched a bug for disappearing user attributes, available on Cloud Retool as of yesterday - please let us know if you continue to see this errant behavior.
Unfortunately we experienced it again yesterday around 5pm Singapore time. The attribute was there when we added it but disappeared shortly after we came back to check.
I would not know as I have not added new external users since then and I am not sure what is the frequency of disappearance - eg. is this something I should look at every day or is it just something that happens immediately after I've added the user?
Sorry you've been feeling this pain. I've landed some changes today that should hopefully address it. Reproing this exact scenario has been challenging on our end, though, so please do let me know if you continue to see it.
@MiguelOrtiz Would you be open to hopping on a call with me sometime this week? We're still struggling to repro this issue so I'm hoping we can figure out where it's breaking for you. Going to DM you.
Same situation here. I set an user attribute in the invitation form. After making login with the invitation I checked the attribute and it wasn't saved
A number of customers have mentioned experiencing the same problem where user attributes aren't saved properly and have to be manually re-entered and saved.
We've submitted an internal bug report for the engineering team to investigate further that has been linked to this conversation.
Apologies for the inconvenience. While we don’t have a timeline for a fix just yet, we’ll keep you updated on the status of the bug report as we learn more!
Then, after logging in with this user, im printing the metadata of that user using JSON Explorer component. This is how it shows up:
This is also the reason why in some apps, where we try to load the attributes from user metadata does not work even if it is set.
Then i go to the user again, change at least one char, save, logout the user and login again, now see how it looks:
This bug cost me hours to find after users complained the could not see some details after logging in, because the metadata could not be loaded to be injected in to the resource queries.
It seems that the initial creation of user attributes is not parsed correctly into a JSON format, instead it is a simple string.
