Real-time "gaps" in Version History visible next day, long after they were needed

The Problem

Normally my Lucid Chart history automatically creates a new version after, at longest, every 10-15 minutes worked. Usually it’s closer to 5-10. So when I ran into a problem that neither I nor the AI could resolve, I would only lose a few minutes when having to restore a previous version to undo the cause.

Beginning yesterday, Wednesday, 10/21/26, the only versions that were visible to me in real-time were hours apart, coinciding only with the times I directly accessed the version history screen when looking for a previous version, or reluctantly, restoring an hours-old version to redo the work.

That said, those apparent gaps of “missing” versions during the previous day became visible and accessible when I started my day today (Thursday, 10/22/26).
 

Completed Troubleshooting

When this problem reared itself again this morning, following suggestions from googling, I did try clearing my browser cache and opening new sessions in Private (Edge) and Incognito (Chrome) windows with no change. I am also certain my organization’s subscription didn’t change on Tuesday, as can be evidenced by Wednesday’s many “missing” versions becoming accessible before logging in today, long after they were actually needed.

It isn’t user-error with the “Show named versions only” toggle. When I toggle it on, only the manually named version show, and when turned off the hours-separated version reappear, but not the “gaps”. The “Load more...” button doesn’t actually load in additional versions.
 

The Question

When visible version history gaps appear in real-time, is there a way to force the version history list to reload and display the invisible (at the time) automatic version saves between those created when accessing the history screen?
 

Context

If it matters, I am working in a very large complex diagram that crisscrosses 7 swim lanes with multiple layers. I keep running into different document-wide “glitches” that I discover after hours of work when I zoom out to look at the diagram as a whole. As a member of IT, I know that “glitch” usually refers to unknown user error. But these are layout-impacting issues, always something new, that can’t be undone manually (at least within my know-how) or by the AI.

Listed below are two examples. Since I only access the history screen every few hours (therefore creating a “visible” version), this is where the real-time version history gaps over the last two days are causing hours of lost work. One example is from yesterday (Wednesday), causing 2 restores (repeating the same 2 hours of work 3 different times) and one from today (Thursday), where I’ve already lost 1.5 hours already this morning, not counting the time documenting it in this post.

1. Three hours after my second restore yesterday, I discovered that around 30-40% of my process elements and connectors, at mostly random locations in the diagram, moved from my “Working” Layer to the base “Page 1” (non-layer). Meaning when I hide the “Working” Layer, almost half of my elements disappear, instead of all of them disappearing as would be expected if properly housed in the layer.
   
   I am constantly switching layers on and off all of the time to make sure elements in each are properly aligning, so I know this had not been an issue maybe 10-15 minutes earlier. As a result, I have no idea what I could have done to select random elements through the massive diagram that would have “de-layered” them from their connected elements in my “Working” Layer. Lucid Chart would NOT give me the option to move them back into any Layer (it was greyed out), and the AI could not move them back, or tell me why (just that they weren’t part of a layer).
    
2. I have everything laid out, and sized, to cleanly fit into a 40px Grid. Everything was fine until I noticed at around 10:30am this morning, maybe 5-10 minutes after my previous column alignment check, that all of the swim lane columns were nudged a tiny amount to the right, so all of the process elements no longer cleanly fit in the document grid.
   
   I expected that I somehow accidentally changed the lane padding, but my actual padding settings were still correct. However, even weirder is that active adjustment to the VERTICAL padding settings stopped having any effect on the swim lanes. The Horizontal padding still made adjustments as you would expect, and changes to both the horizontal and vertical spacing controls were all being reflected in the layout. Only the vertical padding control stopped effecting the layout. The AI couldn’t fix the alignment or identify any issue causing the misalignment.

Any issues like these would normally be easily worked around with only the loss of a few minutes of work, so I’m not necessarily looking for answers to layout “glitches”. However, any potential insight or help on my version history problem would be greatly appreciated. Thanks!