Kindly attach screenshot with the error message. Peter

Hi Fionas,   You're welcome to use anything for your own build. As long as you can pack it into a clientlib you should be fine.   The problem comes that most OOTB codebase, Core Components, Archetype and the rest of AEM systems do not rely on Yarn, instead it's all npm based. Regards, Peter

Hi TB3dock,   Both in regards to your first observation and your subsequent query,   It's all spelled here in fine print: Adobe Experience Manager as a Cloud Service | Product Description   Using Splunk forwarder to ingest logs and then doing maths via Splunk Dashboards to see the approx thresholds ...

Hi Anderspersson,   100% AEM as a Cloud has integration with Splunk, you can use Splunk to perform count of your requests in any shape and form you may wish.   All incoming requests are logged into request.log (for publisher access).   Regards, Peter

Hi Arin,   Justin the original creator of Sling Model Framework does in depth explanation of how Sling Model Resolution works in his slides[1]   Sling models by Justin Edelson (slideshare.net)   Regards, Peter

Hi Neerajsa,   Standard Apache HTTP 2.4 would do,   apt-get install apache2 would do, followed by installing Dispatcher[1[   [1] Installing Dispatcher | Adobe Experience Manager   Regards, Peter

Hi Goyal,   This normally means that service you referenced from your service is not available in OSGi Service Registry.   Regards, Peter

Hi Manikanta,   Would suggest,   sling:match="(.*)cf#(.*)" sling:redirect="http://localhost:4502/editor.html$2"   Regards, Peter

Hi Tam,   Do you see any exceptions in your author logs? Regards, Peter

Hi Manikanta,   First of all we can configure AEM to open in Touch UI by default [1]   In addition we can configure Sling Redirect to redirect any request into cf to editor.html Thus any content author who may have bookmarked old page will be redirected to TouchUI alternative.   [1] user interface -...