I agree, but what is a solution for my situation where I need to query as soon as publish event starts, how do I face this race condition?

I have a custom code with a custom query that runs on publish event through a listener, the query doesnt returns correct results the first time it runs because the property that I indexed has not yet been indexed when the query was triggered, it is a race condition. I tried changing my asynchronous ...

I am on AEM 6.5 non-cloud and I am seeing this error very frequently, I checked each and every place where I am creating resource resolver, I am closing it too and I am not closing any resource resolver that I am not creating for example one through request or session, this isnt causing any function...

This is very strange but for Granite Workflow Purge Configuration I was able to make it work through JSON based configuration instead of XML. created a json config file com.adobe.granite.workflow.purge.Scheduler-myconfig.cfg.json added below configs to the file:    { "scheduledpurge.modelIds":[ "/va...

@EstebanBustamante  com.adobe.granite.workflow.purge.Scheduler is the factory service and it must allow multiple configs either from code or one those are manually added isnt that right?

I have set a environment specific configuration through my code base in config.author folder using OOB workflow purge osgi service i.e Adobe Granite Workflow Purge Configuration, after deploying the code it gets created in local author and works fine but it is not getting created in any of the above...

@arunpatidar  How well it is for lets say we have 10000 of values coming through a remote API and i putting them all in coral-select and applying a filter on it? is that really feasible ?

I have a custom tab in page properties where I have a multifield, the multifield consist of a coral-textfield which I convert to a coral-autocomplete through jquery on page load like below example :     Coral.commons.ready(autocomplete, function () { autocomplete = new Coral.Autocomplete(...

@arunpatidar  how would you do this today when autocomplete and autocomplete-list are deprecated? 

@arunpatidar is there a way we can use runmodes in cq:component node on property component group in case I want to have different groups on different envs say i want to .hidden on PROD?