thank you for the response but updating the aio-cli version didn't work and neither did logging in againDisabling SSL works but can't establish it as a norm in the team so need a more permanent fix for this!

thank you for this but what's the way to troubleshoot this for a more permanent fix?

Nope there's nothing in the custom application code that'd trigger DUMMY event type.The problem is sitemap.xml is a nt:file while the query is looking for cq:Page node which doesn't exist.So even with the correct index for nt:file the query triggered itself is incorrect.

Hey guys, Getting the below error when trying to use AIO plugin to push artifacts to RDE, tail logs etc. Any help or ideas around this? admin-sys digital-adobe-aem % aio aem:rde:install all/target/brandX.all-1.0.0-SNAPSHOT.zip › Warning: @adobe/aio-cli update available from 10.3.1 to 10.3.2. ...

Hi All, We are seeing in our environments 22.01.2025 08:00:11.490 [cm-p10000-e100000-aem-author-bc5d5000d-bhfqz] *WARN* [sling-oak-observation-5] com.adobe.aem.sites.eventing.impl.producer.PageProducerStrategy Invalid change type detected: DUMMY22.01.2025 08:00:11.518 [cm-p10000-e100000-aem-author-b...

Hey guys, Another question for handling of links in AEM Cloud -We have a simple footer component with footer links -href="${columnTwoList.subSectionLink @ context='uri'}"In AMS, the URL is evaulating to /content/a/b.htmlHowever, in AEM Cloud the URL is evaluating to /content/a/b.Query 1 - Why the di...

but how do you restrict the users from concurrently deploying?

Hey guys, Happy new year to everyone! Starting a new year with a fresh query! We want to use our RDE as our DEV environment.RDE inherently is used as a local by developers one dev at a time. The deployment is done currently via aio plugin.But we want to restrict that since DEV environment would be u...

Removing additional minification and disabling processing by GCC would work for this instance but there are another 100+ instances where they are such errors reported!Since the AMS clientlibs is successfully processed without any such error then why is AEMaaCS flagging this as concern?This would mea...

Issue was due to the presence of the Pragma Header chrome extension.It was added to debug request as it passed through CDN. Removing the chrome extension resolved the issue!