Request for Feature Enhancement (RFE) Summary:Provide a way for the "Asset Compute microservice extensibility"/Asset Compute workers to access the default renditions for an Asset so the custom worker can use those as a baseline for further conversions. Either: Pass a default rendition to the work...

Hi @SantoshSai ,thank you very much for your detailed answer! If I might, I would have to follow up questions:What do you mean by "Groovy Script (via ACS AEM Commons)", I know the Groovy Console, but I am not aware, that it is included with ACS AEM Commons, can you point me in the right direction wh...

Hi there, is there a way to find all Assets which have failed Asset Renditions (so they have jcr:content/dam:failedRenditions where the reason is not "RenditionFormatUnsupported")?We would need this information for the following two reasons:- Check for corrupt Assets that can't be processed to manua...

Hi @tmj ,thank you very much! It works now.Maybe something to add to the documentation. Thanks!Anian

If we set "require-adobe-auth" to false in the ext.config.yaml the worker runs successfully. So it seems like, that AEM can't authenticate against App Builder. 

Hi together,HI @Dmytro_Panchenk @yeedg , we have the same issue.Our App Builder Project and the AEM is in the same Org. How exactly did you @Dmytro_Panchenk update the Asset Compute "Adobe IMS Technical Account Configuration"? I can't edit the default configuration. I can create a new "Adobe IMS Tec...

Helpful - yes! But unfortunately nothing that works for us that doesn't include writing custom implementations. I would expect, that AEM can do this out of the box - especially because there are multiple ways which should work, but don't respect the "include children" options for Tags.

Hi @aanchal-sikka ,thanks for your Answer! Unfortunately Option 1 and 2 don't work for us (see the other answers). Option 3 does not work, because we I didn't find a way to replicate a whole tree inside the Cloud Environments (it only works for single Nodes)

Thanks for your answer! Unfortunately, we can't use this approach, because we have some additional logic which hooks into the publish event, which we don't have if we publish the whole package at once.

Hi @AMANATH_ULLAH thanks for your detailed answer! Unfortunately this doesn't work. (See Thread with @lukasz-m above)