Org chart formatting changed and revision history is showing partial data

​@TRK could you try the following steps to help us narrow down the potential cause? Sometimes account performance issues can be related to Internet security/speed or browser issues. These steps will help us eliminate that possibility. 

• Opening your document in a private or incognito window. For help with opening an incognito window, please see this community post.
• Connecting to a different network or disconnecting from your VPN (if applicable)

If those don’t resolve the problem, can you please send the following information?

• A screenshot of the associated Javascript Console output after reproducing the issue. You can open your Javascript Console by pressing Ctrl+Shift+J (if your computer is a Windows/Linux) OR Cmd+Opt+J (if your computer is a Mac)
• A temporary Support PIN for this document. For more information on generating a Support PIN, check out this Help Center article. This PIN is only accessible by members of the Lucid support team, so it can be safely shared within this thread.

Hi ​@TRK, thank you for posting in the community! Have you had a chance to try the steps that ​@aparrish shared above? 

If the issue is still persisting, could you please confirm if this is happening to a specific document? If so, could you please share the temporary Support PIN for the document? You are welcome to DM it to me as well.

This will help me take a closer look at the issue on my end. Thank you! 

Thanks for the replies. The following are results:

• Incognito window same results
• On/Off VPN, and connected to hotspot all the same result

Will DM the support pin to ​@Leianne C .

Hi, thanks for getting back to me with that additional information. I believe you have identified a bug, and I have reported this to our development team. I apologize for any disruption this may cause, and I will update this thread with any new information about a fix. Please follow along on this thread for updates, and post any additional questions or concerns below.

Hi ​@TRK, thank you for the update! I’m glad to hear the issue is resolved. Checking on my end, I can also confirm that our development team had released a fix for this issue. I’m sorry for any inconvenience this may have caused. If you’re still seeing the issue or have any other questions, feel free to reach out. I’m happy to help!