UI Builder changes are being deleted without warning

[Georgi Blue]

I have had several instances were I make a change in the UI Builder (adding a component, adding a client state parameter, updating a client script, and adding a data resource), and after I successfully save the changes, the work is gone the next time I open the UI Builder. Some changes I will have made over a week previous, some the previous day. But when I log in, the work will just be gone.

Most recently, I had 4 different local data resources (all create on different days and saved successfully) in a page variant. They were working and present today around 12:00pm. Around 2:30pm, I opened the UI in a separate window to test and my calls that should be triggered using the data resources were not working. I checked the UI Builder and all 4 of my local data resources were gone. 

I have had this happen before where it takes them a few minutes to load in, but they are now not loading and seem to be just gone. Has anyone had this happen or can explain why or if there is work being done on this? 

[Ashley Snyder]

Is anyone else working on the variant at the same time you are, or perhaps have the pages open and save them with their changes later?

[Georgi Blue]

Yes, there is more than one person working on these variants, but not simultaneously.

Wednesday when I lost the following changes: adding components, adding client state parameters, and updating client scripts (but did not lose my added data resource), I had successfully saved all these changes. Then after checking I had saved successfully, another person began working in the same variant. However, before they did, I do not believe they reloaded the page to verify my changes were there since they previously were working in a different variant on the same page.

Thursday when all of my added data resources were deleted from my variant, no one else was working in my variant before or after. There was another person working in a different variant, but that is all.

Does there need to be a page reload, after one person finishes working on a variant and another begins working in the same variant? Like some caching issue?

[Ashley Snyder · Accepted solution]

At the moment it is suggested that only one developer work in a page variant at a time, or before they begin working to refresh and ensure they can see your variant changes. I'm not sure what the other person had up on their screen, etc. when they began working on your variant but since you mentioned they did not have your variant changes verified before they began working it sounds like they overwrote your variant changes. 

If you're seeing the issue when no one else is working in the variant at all, you should contact HI Support for further investigation into the issue. 

[Georgi Blue]

Thank you! I appreciate you taking the time to help 🙂 Since my changes were successfully saved, I did not think they could be overwritten by another user's outdated cache.

We have been having this issue for some time and have been losing alot of work. Do you know if this versioning/caching issue will be fixed? Perhaps if a user goes to save and has an outdated version, the system would notify them their version is outdated and they need to first refresh? Or whenever an update is made to a variant, if another user has the variant open they will get a warning saying that there are updates, similar to how it does when data resource scripts are updated the UI Builder has a notification prompting you to update?