Thank you @arunpatidar for the knowledge shared and respect for the resilience lesson. Congratulations !

Can you try to manually run the aemsync directly ?Then manually change any file that you expect to get synced and check the console to see if you get any message about that file being synced.

... to../ui.apps/src/main/content

Hi @SwarupYadav I am using this one, which is slightly different:"develop": "webpack-dev-server --config ./webpack.dev.js --env.writeToDisk & watch 'clientlib' ./dist & aemsync -w ../ui.apps/src/main/content"Few things to point out:- You could use & instead of &&.- I prefer to start aemsync at last-...

So you are trying to implement SSO using OAuth. This article covers this use case: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/set-up-aem-sso-authentication/td-p/369707

Hi @Nishanth_KR Is this what you are looking for ? https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/using-oauth-in-aem-6-5/m-p/363355

Hi @Keerthana_H_N  Just few options that just comes in my mind:1. I would try to use a prop as a flag, that can be used as a semaphore for ordering the trigger of multiple sling jobs, each sling job would wrap a workflow that tries to access same resources. For example, each job would first check if...

If I am not mistaking, Expires header comes from origin, and Akamai can be configured to honor this header : https://techdocs.akamai.com/property-mgr/docs/know-cachingIs this what you are asking ?

I meant exactly what you did.Are you sure the other configs get deployed or you have a false positive sentiment that they do. Maybe you can try modify something in another config file and see if it gets deployed. Or maybe you can try a deploy in local on a fresh new AEM instance and see if you can c...

You need to clear apps in order to avoid configs overlapping. Keep only one config for the workflow purge, the one from your codebase.