Thanks!   Can you show an expanded view of the checkout exclusion rule? I'm keen to see how you did that

Hi!   Using Adobe Experience Platform with data coming from Adobe Commerce   We are looking to create a segment for Cart Abandons using the segment Builder The documentation suggests that cartAbandons is measured:  https://experienceleague.adobe.com/docs/experience-platform/edge/data-collection/coll...

Yes - confirmed this is working.   Using:  Latest SDK AEM SDK for AEM v2022.11.9850.20221116T162329Z-220900  Also I needed to update Docker with the "Mac with Apple silicon option" here

I've had issues with the last two updates on AEM as a Cloud Service.  The pipelines and deployments have failed, and the instance needs to be deleted and recreated manually.     The error says "Contact Adobe Support" although as this is a partner sandbox, support is limited.  Just logging the error ...

Hi,I noticed there is a "Sign in" component in the AEM CIF Components github.However there is no documentation for this component on the github page or the AEM Core Components Documentation site Is the "Sign In" Component deprecated?  Will it work with SSO (e.g. if your Commerce engine requires SSO ...

Thanks, I have raised it.  Will reply back when I hear more

Also - regarding your question regarding mod proxy  - No This error occurs running either the default dispatcher src bundled with the SDK or the WKND dispatcher config.

Thanks Jörg_Hoh !  Just confirming yes - it is the latest Dispatcher SDK - aem-sdk-dispatcher-tools-2.0.81-unixI am having a problem with it on an M1 ARM Macbook ProI have also tried running it on an Intel Macbook Pro, and it works fine. From this research online, it appears that this is a permissio...

My Dispatcher is failing with the error Function not implemented: AH00023: Couldn't create the proxy mutex  Looking around, this may be something that can be fixed in the apache2.confIs this something I can edit? Full trace below dispatcher-sdk-2.0.81 % ./bin/docker_run.sh src host.docker.internal:4...

Turns out this is an issue in AEM as a Cloud Service which can occur when the environment is deleted and a new one is created without not deleting the earlier pipeline which still is on an older release. Recreating the pipeline fixes the issue