Forum Discussion
"ParentContainerClosed" Error Prevents Re-Save
I saved a project, made on tiny change and received the error about Parent Container Closed. I've seen years of communication regarding this issue. My frustration is intensified by the fact that this is a known issue that, because "Save As" is a workaround, there seems to be no appetite to fix the core issues. Is it yet known why this only happens after you try to save a change? If you are able to save initially, why are you not then able to resave - even if you are saving to a network drive? Apparently, the network drive is not an issue for the initial save. So why can't this be figured out? This issue has been raised and reraised since at least 2016 (that I can see). So I'll ask you, as I do my child when I'm frustrated... What's the plan here??
Hello LaCara,
Sorry to hear that you ran into this issue.
I understand how frustrating not being able to save a project file can be, especially if you've already spent time making changes to a course.
Working directly on a network drive leaves the saving process susceptible to issues that could be caused by any latency that the network encounters. This is why we recommend working locally when making edits to your project file. Even if the initial save works, there's no guarantee that succeeding saves will work without any issues as full network stability with minimal latency cannot be guaranteed. Other issues, such as third-party applications responsible for file syncing also contribute to the possibility of encountering issues when saving.
If you are unable to work on your project locally, we recommend opening a case with our support team to discuss any possible workarounds.
