Hi @giuseppebag, thank you for the response!We are not using an external service here. The endpoint is AEM Author instance. Connecting AEM Publish to AEM Author by a middleware/external service seems to be an overkill. I am not sure if using runtime to connect AEM Publish to Author is the best appro...

Hi Everyone,    We have implemented the following business use case -  1. Send a request from AEM Publish to Runtime 2. Runtime action is able to generate the access token against the IMS to access the AEM Author instance 3A. Use cURL command to directly ping the author server with the payload -- Gi...

Hi @HarikrishnanBK,A little late to the discussion here but there is an alternative approach of Adobe IO runtime action. You can check out the references below -  1. https://developer.adobe.com/runtime/docs/guides/using/creating_actions/ 2. https://developer.adobe.com/runtime/docs/guides/overview/ho...

Hi @ashish_mishra1,  Divide and conquer - Break the pages into batches (say 500) and schedule them during the off hours.This should help in spreading out the flush events at Dispatcher. Besides the stat file strategy mentioned by @TarunKumar, you can also use CDN purge if you have a CDN (Akamai, Clo...

Hey @NageshRaja ,Has your admin added you to the runtime workspace in the adobe developer console? You can check by logging in to developer.adobe.com   If you do not have developer access, then you will see restricted access info notification as below -  Furthermore, aio:aem:rde is specific to RDE a...

Yes, if the refresh rate is extreme then the cloud pricing model could get expensive compared to LTS deployment where infra cost is capped. But having often seen operation teams struggle with scaling infra to handle traffic surges especially during campaigns, Black Friday sales etc. or ensuring zero...

For most of the business cases jumping to AEM Cloud makes sense. If your use case is the standard WCM + DAM where you want elasticity, zero downtime upgrades, built-in CDN and no low-level tweaks, Cloud is usually the better bet. Other than our government clients who use on-prem to meet security cer...

The root cause is that Adobe Target cannot execute AEM backend Sling Models referenced in your exported HTML because Target only renders static HTML or client-side JavaScriptThe fix for this involved using the "noloudconfigs" to exclude backend-dependent scripts. We validated the export URL /content...

Try "aio where" - This should give you Org, Project and Workspace.If its empty then you need to run "aio login'" - Post authentication run the below - 1. aio org:list -- view all organizations 2. aio org:select  3. aio project:list 4. aio project:select 5. aio workspace:list 6. aio workspace:select ...

Hey @NageshRaja, Your implementation class is not implementing ComponentExporter. public class MultifieldCollectionModelImpl implements MultifieldCollectionModel, ComponentExporter { You will need to add a getExportedType() method.@Overridepublic @NonNull String getExportedType() { return resource.g...