Product Communities

We have been attempting to connect Workfront and Campaign Classic V8 with Fusion and we established the connection.    The issue we seem to be having when using Adobe Campaign Classic Read a Record module, is that when selecting any resource, we get this error message.   I have been working with the Campaign Classic admin to see if we can troubleshoot the access limitations and just been hitting a roadblock at this time.     Does anyone have any experience with this and know how to correct this?   This appears to be something on the Campaign Classic side that is limiting access and I am not familiar with the application and hoping I could help provide the admin over there some possible solution to review.   Thanks!  

I had the pleasure of speaking at an Experience League Community AMA at Adobe Summit this year, and I wanted to bring the conversation here for those who couldn’t make it. This is the kind of thing I genuinely wish someone had told me before we started.AEP on AWS  - Summit AMA RecapThe ContextWhen we set out to implement Adobe Experience Platform (AEP), the working assumption was that it would behave like any other cloud deployment. It didn’t. AEP’s defaults around networking, identity models, and tooling integration had been built against a specific cloud environment. That wasn’t documented anywhere, it was something you discovered by running into it. In our case, we discovered it during an architecture review, well into the project, not in a test environment.On top of that, Real-Time CDP and Customer Journey Analytics had to go live at the same time. That meant every foundational decision from schema design, identity resolution to data integration had to be right for two production s

Join us for this upcoming session including Q&A time with Vengadesh Shanmugavelu, AEM Champion and certified AEM Architect and Lead Developer.Learn From Your Peers Webinar | Adobe Experience Manager Assets WebinarDeliver Once, Delight Everywhere: Scaling Omnichannel Experiences with Adobe Dynamic Media Are you wondering how to streamline the transformation and optimization of your images and videos in AEM Assets?In this Learn from Your Peers session, Adobe Experience Manager Champion Vengadesh Shanmugavelu will share:How Adobe Experience Manager Dynamic Media enables intelligent media distribution using profile settings, smart renditions, and real-time optimization. How to activate Dynamic Media through AEM Core Components and extend its power across the enterprise using Dynamic Media Open APIs.Whether you’re a marketer, architect, or developer, this webinar will show you how to deliver once and scale everywhere with performance, consistency, and control. Date and Time: Thursday, M

We are about 18 months into a mature AEP + RTCDP implementation and have crossed 400 active segments across business units. We are starting to see non-trivial evaluation latency on streaming segments during peak ingestion windows and our architecture review flagged segment sprawl as a likely contributor.Adobe's documentation sets technical limits but doesn't offer much guidance on the operational governance model to prevent getting there particularly in a large enterprise where multiple teams (CRM, digital, paid media, product) all have write access to the segment builder.A few things I'm genuinely curious how others have solved:Do you enforce a segment approval workflow before publish to production, and if so, is that a process control or is there a technical gate you've built?   How do you handle segment ownership when the original creator has left the team? Orphaned segments with no owner are our single biggest hygiene problem. Have you seen a material performance difference between

I have the below network request { "events": [ { "xdm": { "eventType": "web.webpagedetails.pageViews", "web": { "webPageDetails": { "URL": "https://www.xyz.com" }, "webReferrer": { "URL": "https://www.xyz.com" } }, "device": { "screenHeight": 800, "screenWidth": 1280, "screenOrientation": "landscape" }, "environment": { "type": "browser", "browserDetails": { "viewportWidth": 1265, "viewportHeight": 150 } }, "placeContext": { "localTimezoneOffset": -330, "localTime": "2026-05-08T09:54:09.711+05:30", "ianaTimezone": "Asia/Calcutta" }, "timestamp": "2026-05-08T04:24:09.714Z", "implementationDetails": { "name": "https://ns.adobe.com/experience/alloy/reactor", "version": "__VERSION__+2.34.2", "environment": "browser"

If the JSON is not flat is it possible to use Data Prep??

If you just got back from Adobe Summit 2026 (or wished you had), this is the event you don't want to miss. The Workfront WUG – Southern California is hosting a virtual after party on May 12, 2026 — and we're skipping the polished recaps in favor of the real conversation.What announcements will actually change how your team works? What's worth bringing back to your org — and what's just hype? Our expert panelists are ready to give you their unfiltered takes on Workfront, content supply chain innovation, and AI. No fluff. Just clarity, candor, and a little healthy debate.🗓️ May 12, 2026 | VirtualAll chapters, members, and guests welcomeRegister here: https://workfront-augs.adobe.com/events/details/adobe-workfront-wug-southern-california-presents-spill-the-tea-adobe-summit-2026-after-party/Mega-WUGs are special virtual events where all Workfront User Group (WUG) chapters are invited. Not familiar with WUG?  Learn more here.

I’m curious who is using Priorities and whether it’s working well for your team. I’ve been playing around with it for a while and really like the UI and overall functionality, but it still feels a bit too “clicky” for me to comfortably roll out to our teams.For example, our Creative team lives in their assigned tasks and frequently jumps into the project custom form to view requirements/details. In Priorities, it seems like they need to click into the project name and then click “Go to details” from the side panel to get there. Am I missing an easier way to navigate this?Would love to hear how others are using Priorities in similar workflows/scenarios.

We have Workfront contributors that will view a monthly report that contains a proof link, where they can view a document proof. For these users, all User notification settings set to off. However, when they click to view the Document Proof, Workfront is adding them as a “Reviewer” to the Document Proof and automatically subscribing them to receive Daily Summaries for that project. We tested resolution by keeping them as Reviewer with Proof notification settings disable. However, next month when they view the report again, it auto-defaults to start sending Daily Summaries. This is an issue, as these particular users cannot get bogged down with the details within those daily summaries for each project, and we need to control this scenario to protect their inbox.Has anyone else experienced this and/or found a resolution? I saw a past post in Experience League, but it was marked as “resolved” due to inactivity on comments, but with no resolution.

I'm struggling to find an efficient way to debug Recommendations. With at.js, I used mboxTrace, which provided a very clear "Recs Box" showing exactly which criteria were used, which entities were returned, and why certain items were excluded.Now that I'm using Web SDK and the AEP Debugger, I find the debugging process much more difficult. I can see the network calls, but I miss that high-level summary of the Recommendations logic.What I've tried: Using the AEP Debugger Extension to look at Edge Traces. Digging through the interact response payloads in the Network tab. My Questions: Is there a way to get a visual "Recs box" similar to the old mboxTrace functionality in at.js? In the AEP Debugger, where exactly should I look to see the Criteria details and Exclusion reasons for a specific Recommendations activity? Are there any third-party tools or specific "Edge Trace" configurations that make the JSON output more readable for Recs-heavy implementations? How do you effectively

Hi ,We are working on profile capping in a recurring journey. Profile capping should also work on a recurring journey which means the counter should get reset to zero .But from the adobe documentation i came to know that , When profile cap is defined on a recurring journey, the counter does not reset after each recurrence.The counter applies only to the selected journey version. The counter resets to zero when the journey is duplicated or when a new version is created. After a reset, the entering profiles take the nominal path again until the counter limit is reached.So, is it possible to reset the counter so that in a recurring journey profile limit will work . ThanksUsha

EDS edge workers can be suitable for API authentication. Please provide your comments

Overview:Enhance the navigation experience within the Adobe Journey Optimizer canvas by introducing modern, intuitive controls aligned with industry-standard tools.The current navigation model requires users to independently manage vertical scrolling, horizontal scrolling, and zooming through separate UI controls. This creates friction when working with complex or large-scale journeys.This idea introduces:Omnidirectional canvas movement via middle mouse click + drag Scroll wheel-based zoom functionality A more fluid, continuous navigation experience Current challenge:The existing navigation approach has several usability limitations: Fragmented navigation controls Vertical movement: scroll wheel or scrollbar Horizontal movement: bottom scrollbar drag Zoom: separate UI buttons Linear movement only Users cannot move diagonally across the canvas Requires switching between horizontal and vertical controls High interaction cost Multiple clicks and manual dragging required Navigation

I'm trying to retrieve Marketo assets (emails, forms, snippets, etc.) filtered by workspace. While the Folders API works for most assets using folder-based  filtering, I'm facing two issues: 1. Landing Page Templates: They don't appear in the folders API response and aren't folder-based. The /rest/asset/v1/landingPageTemplates.json?workSpace=<name>  parameter returns templates from all workspaces instead of filtering by the specified workspace.2. New Editor Assets: Folders with folderType: "Email Acrite" (New Email Editor) return "Invalid folder type" error (code 711) when queried via /rest/asset/v1/emails.json?folder={...}, even though these folders appear in the Folders API response. What's the correct approach to retrieve these assets filtered by workspace? Is there an alternative API endpoint or method I'm missing?  

Fusion currently supports Google forms only. MS Forms would be a great addition.

Hello, I have a user who seems to have all-but-Admin rights to AEM Assets, and has access to Content Hub. He is however unable to share Collections. When he creates a Collection, the only option for who has access is “Only you and admins can view and edit”. He says he has previously been able to create a collection and give public access, but this was only to one Collection. We’ve not been using Content Hub for too long so not sure what I might be missing!Thank youLana 

Yelahanka has become a preferred choice for homebuyers seeking a modern lifestyle with peaceful surroundings in North Bangalore. The area is known for its planned development, wide roads, and green environment, which together support comfortable daily living. Residential growth in this region has been steady, driven by improved infrastructure, good connectivity, and rising demand from families and professionals. Buyers exploring upcoming projects in Yelahanka can find well planned developments that focus on quality construction, smart layouts, and long term value.New housing options in Yelahanka are designed to match current lifestyle needs, offering better ventilation, functional spaces, and essential amenities. Many new apartments in Yelahanka are part of gated communities that provide safety, open spaces, and community living benefits. These homes suit families looking for convenience, comfort, and easy access to schools, hospitals, and daily essentials.For buyers interested in inde

Hello Adobe Team, currently modern image formats are not fully supported end-2-end.In the CF EditorAVIF = Asset reference can be selected, NO preview image shown to authors. The delivey through Dynamic Media with OpenAPI is workingJPG XL = Asset reference can be selected, NO preview image shown to Authors. The delivery through Dynamic Media with OpenAPI is NOT able to render it. Thanks,Tim

Hi all,we are registering API client ID’s in an api.yaml (see https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/open-api-based-apis) and deploy them with a config pipeline.The documentation describes that for secrets can be used placeholders (see https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/config-pipeline) Something like shown here seems not to work: kind: "API"version: "1"data: allowedClientIDs: author: - "${{MY_AUTHOR_CLIENT_ID}}"We added the values as secrets with “Service Applied: All” in cloud manager configuration but it only works with specific values directly in the api.yaml.Do you know if this not supported kind: API?Best,Mark

Hi community,  We want to share details about a critical issue affecting AEM 6.5 LTS SP1 and AEM 6.5 LTS SP2 customers who perform offline compaction using oak-run.  --- What is happening  After running offline compaction via `oak-run compact` followed by two rounds of online garbage collection (GC), AEM instances were throwing SegmentNotFoundException (SNFE) and becoming inaccessible.  Who is affected  Customers on AEM 6.5 LTS SP1 or SP2 who have run offline compaction with an oak-run jar that does not include this fix. This was a blocker for all customers upgrading to AEM 6.5 LTS SP1/SP2.