@NicholeVe You can try using AEM launches for this.  https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/launches/overview  

@nbg19a Thread safety is primarily the main concern with getting the session by adapting the resolver.   A very good read on a very related topic by @joerghoh can be found here - https://cqdump.joerghoh.de/2013/07/23/cq-development-patterns-sling-resourceresolver-and-jcr-sessions/  

@SriramDhayal    What is the specific role of reference-adjustment-service in AEM, and in what scenarios does it get triggered? Reference adjustment service comes useful when you are migrating/moving your assets from one path to another. The resources where these assets are used would need to use th...

@san_11 You will have to convert the jars into an OSGI bundle. OSGI container needs bundles and not plain JARs.

@gvaem try  Authorizable publisher = userManager.getAuthorizable(workItem.getWorkflow().getInitiator());

@jezwn Deleting the package-lock.json and re-running the pipeline should do the trick.

@abhishekanand_  Can you please elaborate on your use case?  As @EstebanBustamante mentioned, there might be other options available for your need instead of customizing the ACS commons list.

@pruthvira Most likely the project bundle is in installed state. Can you check that ?

@30991930w169 That is not possible with AEM as cloud service. But you could combine the code in the two repos into a single repo with individual repo code as submodules and then deploy. 

@Nandujee You might want to consider using external service providers for sending emails on that scale. You could use something like a Amazon SES for your use case.