Welcome @JulianTo1 - love the "puzzle pieces" name. Out of interest are you using AEM 6.5 or Cloud Service?

Hi all and welcome to Experience League - looking forward to meeting you and helping you get the most you can out of this awesome community.   Martin  

I would recommend to raise a support ticket, however I suspect that GLB and other 3D formats are not officially supported for delivery with Dynamic Media Classic.    If you have your own CDN layer infront of AEM DAM you may be better to simply expose these types of files directly as DM would only be...

The cloud service instance i tested on is running version 2025.1.19352.20250131T194709Zyou can check the version in Cloud Manager for each environment On my sandbox env it shows the following as the latest version available currently: 

I'd agree with the others - nested CFs is generally the way to go and with the new CF editor view, navigating between them is much simpler than it used so be. Sticking to standard field types is particularly important if you're accessing it via GraphQL as it understands how to putput standard conten...

Tags are also a tree structure so you can break things down into more and more specific categories, and only allows users to select from a pre-defined list, whereas other metadata fields are essentially free text. For your industry use case this would ensure you don't get subtle variations on the sa...

Are you able to confirm if this is on AEM as a Cloud Service, or 6.5?  Does this happen for all pages, including newly created ones? Do you see anything in the error logs at the point of this request? As Kostiantyn said - if you can share the full stack trace and content of the 500 response, this ma...

I would recommend logging this as a bug as your query syntax looks perfectly valid.I can't reproduce the error with similar queries.  Are you on cloud service on the latest release?

The issue is likely linked to the fact the editor makes use of an iframe to render the page and this must be affecting how the height is calculated, causing it to believe the height encompasses the full content of the page, not just the visible viewport. Do you have a meta tag for viewport?  setting...

Agreed - /bin and /content are accessible by default for anonymous access, but other paths would require you to force a login on the publish instance.