# Very Scary Project Experience Last Night! **URL:** \ **Category:** Elements\ **Created:** [April 24, 2025, 6:31pm UTC](https://forums.realmacsoftware.com/t/very-scary-project-experience-last-night/47293 "2025-04-24T18:31:31Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![handshaper](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/handshaper/32/27373_2.png) [@handshaper](https://forums.realmacsoftware.com/u/handshaper)\ **Post date:** [April 24, 2025, 6:31pm UTC](https://forums.realmacsoftware.com/t/very-scary-project-experience-last-night/47293/1 "2025-04-24T18:31:31Z")
@dan Yesterday I got my newest website live and was really happy with how it all worked out. I had not shutdown Elements in a few days so I decided to close all of the open projects I was working on. When I came back to open the newest one I got a dialog telling me that the document was repaired and X number of items were recovered. Scared the hell out of me. Below is the dialog that was displayed. ![CleanShot 2025-04-23 at 19.49.53@2x](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/8/8/8887162d58cae218875f570d86928b324d89aa6c.png) When I was finally able to get to the home page there were a bunch of large image placeholders at the top of the page. I deleted them, which did not seem to affect the layout of the page, so I have no idea what exactly the problem was. I then tried to save the project after performaing this cleanup and it would not save the project. So I quit and tried again. Same dialog popped up. This time I removed one item and saved and it worked, so I slowly repeated the process until all of the image placeholder were gone. Once again I was able to save the project. I then made a copy just in case. But now I’m extremely hesitant to close this proejct in case I’m faced with the same issues. I’m trying to think what was going wrong with the project as the other two I had been working on at the same time did not have this problem. I then realized the only thing that was different about this project was the fact that I had added PAGE ICONS, could that have been the problem? I’m about to try closing the project again to see if the problem returns, but before I do that I’d really like to know what this “missing parent” issues means and where I should go looking for the problem. Needless to say this was extremely disconcerting as I had just spent ten days creating this project and the thought of possibly having to start over was daunting. I shoudl also mention that I did try the backup that was created when the site was first uploaded and it had the same issues. ---
**Author:** ![miketee](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/miketee/32/27560_2.png) [@miketee](https://forums.realmacsoftware.com/u/miketee)\ **Post date:** [April 24, 2025, 6:47pm UTC](https://forums.realmacsoftware.com/t/very-scary-project-experience-last-night/47293/2 "2025-04-24T18:47:34Z")
I had one of these dialogs yesterday too!! 😮 On a pre-made project I had been modifying…had deleted a few pages to make a one-page “coming soon” site. Something very simple with only a handful of components. Perhaps because I broke some Globals? Not sure either! Yikes! ---
**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\ **Post date:** [April 24, 2025, 10:12pm UTC](https://forums.realmacsoftware.com/t/very-scary-project-experience-last-night/47293/3 "2025-04-24T22:12:48Z")
Don’t panic, this is nothing to be alarmed about. **Your project(s) are safe!** [Elements](https://elementsapp.io/) is just tidying up the document and putting any orphan nodes it finds at the top of the page. These can safely be deleted. We will improve this over time, but for now, don’t worry. Just tidy your project and save off a new version. **Slightly more in-depth explination for those interested…** When an object is deleted, the corresponding node and all of its child nodes should be recursively removed from the structure. However, this expected behavior doesn’t always occur reliably. The issue you’re encountering arises because [Elements](https://elementsapp.io/) is currently removing the parent node _before_ processing and detaching its child nodes. This sequencing can lead to orphaned nodes or inconsistencies in the document structure. We’re aware of this and will be making improvements to the deletion logic to ensure it’s more robust and handles these edge cases correctly. ---
**Author:** ![handshaper](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/handshaper/32/27373_2.png) [@handshaper](https://forums.realmacsoftware.com/u/handshaper)\ **Post date:** [April 25, 2025, 1:07am UTC](https://forums.realmacsoftware.com/t/very-scary-project-experience-last-night/47293/4 "2025-04-25T01:07:49Z")
> [@dan](#): > > Don’t panic, this is nothing to be alarmed about. **Your project(s) are safe!** @dan I have every faith that you will do the right thing and that all of this come together in due course. It really helps to know what is causing this as that makes it seem a lot less threatening. The main thing that had me worried was after I deleted these orphaned items I could NOT save the project. So I tried again and it appeared I should have been doing some saving in between deleting them because that fixed the problem ---
**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\ **Post date:** [June 14, 2025, 4:52pm UTC](https://forums.realmacsoftware.com/t/very-scary-project-experience-last-night/47293/5 "2025-06-14T16:52:00Z")
I had this experience today! 🤔 ![CleanShot 2025-06-14 at 17.47.22](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/e/3/e325bc4620f89ca78d66e2a99c685976fe1c3488.png) I opened my project late this afternoon, for the first time today, and it was filled will lots of \< recovered \> components across multiple pages. So I quit the project, and duplicated it for a backup. [Carbon Copy Cloner](https://bombich.com) came to the rescue. As I take backups every hour to an SSD (takes 15-30 seconds on average) I was able to go back to a backup snapshot taken yesterday and recover the project from the save before the one that has this issue. I had only been experimenting with Modals since yesterday’s save and fortunately nothing important has been compromised. 😮‍💨 ---
**Author:** ![tpbradley](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/tpbradley/32/25503_2.png) [@tpbradley](https://forums.realmacsoftware.com/u/tpbradley)\ **Post date:** [June 14, 2025, 6:51pm UTC](https://forums.realmacsoftware.com/t/very-scary-project-experience-last-night/47293/6 "2025-06-14T18:51:44Z")
@logrunner Can you remember if you changed any globals when this happened? ---
**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\ **Post date:** [June 14, 2025, 9:40pm UTC](https://forums.realmacsoftware.com/t/very-scary-project-experience-last-night/47293/7 "2025-06-14T21:40:23Z")
I am fairly certain I was playing around with globals, copying and deleting stuff etc. However, I can’t remember now, exactly what I was doing. I saved the project yesterday and the problem only manifested itself when I re-opened the project again this afternoon.