That error likely means your test is calling addModelsForClasses(...) on the wrong context type. In JUnit 5 with AEM Mocks 5.x, addModelsForClasses() lives on the Sling/AEM context. If your variable is typed as OsgiContext/OsgiContextImpl, the method doesn’t exist—hence the error.(also see related d...

Thank you for your reply @Srikanth23696837zrx0 . If skipping tests makes the build green, then the break is likely in your test toolchain/code. I’d treat BDTagsReferenceWorkflowTest as the culprit. Try the following (if applicable and/or not done already). I suggest trying one by one and always try ...

Based on recent pain, I suggest double-checking on the following: Check your pom.xml to make sure correct Apache POI dependencies (org.apache.poi) declaredRun mvn dependency:tree to inspect your dependencies tree and identify any issues, especially around transitive dependencies. Rather simple answe...

Hi @AbhishekTr1 , reg. your questions:1. The script approach you took seems legit to me (class name and size check)2. If minRecordLength is not shown, AEM is using the default value, which is 16,384 bytes (16KB). (see https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implement...

hi @georhe6  I can confirm experiencing similar issues in the past. Contacting Adobe was the way to go.  Have you tried creating a "clone" of that pipeline and see if that goes through?

I believe this is now in place as seen in https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/log-forwarding#setup

@Jose_Manuel1 I think it depends on the customization in place. If you have customized the AEM UI this is already an orange (if not red) flag for AEMaaCS. Afaik the only commerce integration approach officially supported by Adobe for AEMaacS is CIF (https://experienceleague.adobe.com/en/docs/experie...

Understood - and indeed, to the best of my knowledge there is no way to do so via OOTB UI. Here are some alternatives I can think about (hint: development required). If it is a "one-time" activitiy, my choices would both be related to scripting:1. use the Groovy Console plugin (powerful, applicable ...

Would the alternatives mentioned here work for you? https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-assets/how-to-bulk-update-metadata-in-aem-assets/m-p/573132 

Do you have any way to debug and observe the request pipeline, e.g. via dispatcher logs? That is usually a first stop. Is there a chance the servlet OSGi config is missing for stage and the servlet has a config policy set to "required"? These are my first thoughts just based on what you mention abov...