I have create workflow launcher which need to be trigger when new content fragment is created under /content/dam/myfragments folders.   But considering with in content fragment any nodes getting created under the parents node there are multiple workflow instance triggered for the same content. . I b...

The issue is resolved. My bad this issue was appearing due to office proxy restriction. With personal internet connection it is working fine. Unfortunately in logs I did not find any mentioned on proxy or connection issue so it took time to figure out what is causing the issue.

I am following the tutorial mentioned in adobe link https://docs.adobe.com/content/help/en/experience-manager-learn/sites/content-fragments/content-fragments-delivery-feature-video-use.htmland in that specific section "Using the Assets HTTP API" . There is sample CURD operation available Example POS...

I am using AEM version 6.5.2 and still seeing this issue when try to create Content Fragment.*WARN* [sling-threadpool-a4d71255-ffbc-4303-aef9-ed7d1b918a48-(apache-sling-job-thread-pool)-14-<main queue>(ref-updater/delete)] org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex This index...

Check if this example help.https://engineering.icf.com/using-a-content-fragment-api-in-react/

I believe if the code exceeding the specific limit in given file you will see this exception. You need to have the logic split in 2 different file.I followed the same approach and it worked.

Update on the above solution.The deleted out of box index reappear on restart of the instance and we started noticing the issue again. After further working with Adobe support team, here is the updated solution.Step1: open the object in crx/de : "/oak:index/ntBaseLucene/indexRules/nt:base/properties...

Issue is resolved by Adobe Support Team. It is bug in AEM 6.3+ SP1 + CFP2 , instance having more DAM assets will face this issue due to wrong index value.Problem : Asset delete causing slowness Root cause : Cannot be efficiently handled by the ntBaseLucene index because it is (intentionally) not con...

We are recently migrating from AEM 6.1 to AEM 6.3.In Production we have large DAM assets content and post migration we identified that in AEM 6.3 if you delete any single DAM assets itself it gives the exception as The query read more than 500000 nodes in memory. To avoid running out of memory, proc...

Hope you are aware about AEM 6.2 onward there is configuration available in AEM and threshold is setup to restrict any query execution which may cause impact to instance.For AEM 6.0 - 6.2 versions, you can tune the threshold for node traversal via JVM parameters in the AEM start script to prevent la...