yes to me it happens when i am working with a very big configuration.. but the truth is, once i stop editing and messing aroung with the configuration, once is stable and fully loaded, it remains that way. is odd.
The only possible reason I could explain this, is that you might simply have to wait a bit for all jetways to be recreated again, before touching the editor so, depending on your system speed (and antivirus can play a big part in this, and your fps as well), the time to reload a configuration might be longer than usual.
Also, the cache regeneration process is a *multithreaded* process, which runs in the background. If it wasn't, your simulator would be brought to an halt during the cache regeneration. But it also means that something unusual you do while the cache is being rebuilt, might result in problems.
For example, Javier just told me he used the "Go To" airport menu to jump to a different airport while he was editing one, with the scenery customization page still open. This is an example of something "unusual", that I never thought someone would try... but yes, we'll try to detect this situation as well and prevent it.
In general, there are just countless of things you shouldn't probably do while editing a scenery, like switching the airplane with the scenery customization page open, disable/enable a scenery in the Scenery Library while you are editing it, restarting Couatl with the scenery customization open, slewing away from a scenery with the scenery customization page open, using external utilities to change the airplane position while editing, moving the joystick while editing, using 3rd party utilities that do strange things with your positions while editing, entering/exiting Avatar mode while editing, and the list go on and on, we simply cannot possibly anticipate any possible thing you might want to try while editing a scenery.
Basically, don't do anything other than using the allowed editor keys while editing, and you can be sure everything will work as expected. Is not that we don't use the editor ourselves and, when we do a customization for an FSDT scenery, we use the same editor everybody uses for several hours straight, with *countless* of Couatl restarts and, of course, it never fails, and when it does, we immediately fix the problem and push the update, because we made the editor even for our own use.
If you find that you must do something that looks convoluted to you, and you need it for editing, then please describe why you are doing it, and we might improve the editor to allow you to achieve that goal without requiring to do whatever strange thing you do which might cause problems to the editor in the first place.