Nested Content Issues

I’ve been trying to create blocks with content areas, where some blocks are nested inside others due to the structure. I’ve identified two scenarios:

Manual tree creation from scratch:
When building the “tree” manually, the CMS seems to save the changes, but those changes are not published in the corresponding child block. Instead, they appear to be stored at the top-level parent component. As a result, the system detects that nested components exist, but their configuration/content is missing — leading to empty components being sent to the frontend.

Using pre-existing components:
When assembling the “tree” using already created blocks, the system correctly detects and publishes them. This suggests that the issue specifically affects newly created components within the same tree.

This behavior can significantly impact the content editing experience, especially for users familiar with the CMS PaaS, where nested content creation and publishing works seamlessly.