Product Communities

Hi Team, Could you please provide your guidance on the following?We recently created an llms.txt file under DAM with some content in it. This file is accessible via the domain (for example: https://www.mycompany.com/llms.txt). URL shortening is being handled through the dispatcher, and the file loads successfully in the browser without any issues. However, when we try to access the same URL through Gemini or any gpt and request it to read the content, it returns an error stating that the file is not accessible or not available on the domain. Since we have Microsoft CDN and AMS WAF rules in place, could you please advise whether we need to validate this at the CDN layer, AMS App Gateway WAF rules, or the dispatcher level? Thanks in AdvanceRegradsVeera 

Is it possible to set a default filter in Workload Balancer? I would assume you can do this in Layout Templates, but I do not see a way to do this? The problem I am having is users that are going to the WLB for the first time do not have a good default filter selected, so when they click on the WLB they’re inadvertently trying to load a ton of data and the page takes forever to load or times out. 

Exited to host this even with Adobe AEP Product Manager.Join us for this virtual session where Adobe Product Manager will showcase the latest upgrades, features, and best practices for B2B use cases in Adobe Experience Platform and connect directly with Adobe experts and network with fellow professionals.Event is scheduled on June 24, 2026 at 3 PM CST.Register here: https://bit.ly/4g5Sp0r

 I’ve been facing an issue in RTE where the links with .aspx extensions were flagged as invalid by linkchecker. Hence I added a override pattern in com.day.cq.rewriter.linkchecker.impl.LinkCheckerImpl.cfg.json with the below pattern:"service.check_override_patterns": [  "^system/",  "^.*\\.aspx(?:$|[?#].*)"]Note: “^system/” was added as default.Even after this change, the .aspx links are still getting flagged as invalid in the linkchecker even though they are valid web pages. How can I fix this?

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

Is such a dataset created for every specific merge policy created in the sandbox?

As we know the External Lookup field fetches data using REST API and has been part of Workfront for some time. Although it can be game changer, the desired features are still not integrated.Authentication API Secrets manager Auto trigger the API.This post is to highlight one feature which would be great to have: auto triggering the API and showing the result. Why is this feature important to you?Many a times there are clients who ask for fields that are auto-populated based on other field selections. Other platforms offer this feature with their product but workfront is still tralling behind. With auto triggering enabled for External Lookup, it opens the door wide open for so many possibilities.  How would you like the feature to work?In the custom form editor add a checkbox to say - Auto trigger A new field should show to select the desired output of this trigger. Since data can be an array, we would select first object (example) On a Workfront object, this would translate to auto pop

Problem statement:Customers encountering blocking and duplicate-key failures during concurrent Update Data or registration-style operations currently have no Adobe-supported product feature to smooth write contention. Public guidance focuses on maintenance and scheduling, and product guidance does not recommend enabling SQL Server RCSI. ACC should provide native controls and diagnostics to reduce lock contention without requiring unsupported database isolation changes.Request:Provide native concurrency controls for ACC write-heavy operations on SQL Server so customers can reduce blocking and duplicate-key failures without changing unsupported database isolation settings.Possible sub-features:Queue/throttle mode configurable queuing/throttling for high-concurrency write paths, including registration or subscription-style calls Conflict-aware workflow scheduling/locking hints for Update Data activities targeting the same dataset; lock-aware diagnostics and admin visibility Application me

The Project Falco beta program grants you exclusive access to an updated version of Adobe Journey Optimizer B2B Edition that is specifically designed to supercharge your Marketo Engage instance (no purchase required).Program highlights• Agentic Program & Journey Creation: Design and optimize omni-channel lead journeys inseconds leveraging your existing programs, campaigns, and channels inside Marketo Engage.• Agentic Audience Segmentation: Prompt the audience agent to automatically discover andcreate audience segments using Marketo Engage data.• AI-powered Decisioning: Achieve next-gen personalization through AI-powered Next-bestJourney and Journey Path decisioning.• Omni-channel Orchestration: Connect and activate inbound and outbound channels togetherfrom a single journey canvas, expanding to web and paid channels.• Agentic BDR Experience: Allow your BDR teams to automate outbound sequences using theAccount Qualification Agent together with integrated marketing data.What you getE

I am working with a customer who recently purchased Designer 6.5. When the log into https://licensing.adobe.com and go to the download section, that site is secure. However, when they click on the download button, it opens in a new window that is not secure and we get an error that says 'can't be downloaded securely'. Is there any way we can get a secure direct download link or some other way to down load the installer?

Can someone explain what a “Root Project” is and how they could be used? I’m working on a report and noticed values for “Root Project” as an option when I add a column. I can’t find any documentation on that value or any fields with that name. None of my projects have any value in any of those fields when I include them in a report. Our large campaigns use a project for concept development. We add a project for each type of deliverable and link them together in a program. It might be valuable to us to name the concept development project as a root project. 

Assume that I have multiple Data Views. If I want to switch between them in Workspace then corresponding metrics in Data Views have to have same Component ID? 

I have implemented the Adobe Analytics MCP via oAuth server to server authentication and currently I am able to create connection and maintain sessions for this. However while using the call tools to request and fetch data from any reportSuite I am facing some kind of bug for the tool “findMetrics”.Even after using the “page” & “limit” params I am still getting a large set of data as a response.for e.g. I requested “page”:0 & “limit”:10 but still got returned 86 rows of metrics data, Not sure if this is any issue from server side under which “limit” is not recognized. If anyone else faced this error let me know. For now I have restricted the data by manually slicing the  post my limit.

Hello everyone,I wanted to get your feedback and suggestions on steps to follow while starting on implementing analytics for AEM Adaptive forms in a headless setup.Since a JSON flows back from AEM, should AEM responsibilities just be restricted to maintaining standard field definitions and the rest of the tagging happens on the front end renderer (React) ?Any pointers would be greatly appreciated.

Personalization often starts with a simple customer moment, but turning that idea into working template logic can take time. You may need the right field path, helper, condition, date format, and fallback behavior.AI Assistant for Personalization Expressions helps reduce that friction by turning plain-language intent into AJO personalization template logic you can review, preview, and apply.Instead of starting with syntax, you can start with the outcome you want for the customer:Use the customer's renewal date, add one year, and format it as MM/dd/yy. If the renewal date is missing, do not show the date.It helps translate that request into template logic you can review, validate, and use in AJO. What AI Assistant for Personalization Expressions Helps WithIt is available from the AJO personalization editor through AI Assistant. It helps when you know the customer experience you want, but need help writing, understanding, or fixing the template logic.Generate new personalization expressi

In the first part of this series, we explored the essentials of Adobe Journey Optimizer (AJO) error codes—why they matter, how to approach them, and how quickly understanding these signals can transform your troubleshooting experience.In this second installment, we go a step further and include more frequently encountered error codes. We’re presenting a curated, in-depth table of even more AJO error codes you’re likely to encounter as you build, test, and launch omnichannel campaigns. Think of this guide as your “cheat sheet” for campaign health: If the mysterious codes below pop up in logs or UI banners, you’ll know exactly where to look, what likely caused it, and how to get unstuck fast.Whether you’re facing backend 500 errors, validation problems, or puzzling runtime glitches, this list breaks down each code’s context, root cause, and practical steps to resolve or avoid it. Keep this resource handy—it’s designed to help your ops, technical teams, and marketers spend less time stari

Hi All, We have used sling:resourceType="cq/gui/components/authoring/dialog/fileupload" have in our AEM components along with enableNextGenDynamicMedia as “true” to connect to Remote DAM instances. Our Polaris URL for video is of the format as below - https://delivery-p123456-e98765432.adobeaemcloud.com/adobe/assets/urn:aaid:aem:a64f4a64-0af2-4991-ghg4-68542aae43e4/as/1f605fcd-xyz-Jumpstart.mp4Directly hitting on browser gives 404 - {"type": "https://aem.api.adobe.io/problems/not_found","title": "Not Found","status": 404,"detail": "Item doesn't exist"}How we render it in our DOM is FED based on ReactJS takes the URL and renders the DOM as below - <div class="video-container"> <span data-component="BannerVideoModal" data-props="{ videoUrl: https://delivery-p123456-e7654321.adobeaemcloud.com/adobe/assets/urn:aaid:aem:a64f4a64-0af2-4991-9d62-68542aaef544/as/1f605fcd.mp4, videoThumbnailUrl: , videoType: videoEmbedded, enableAutoplayMode: false, enableUnm

Hi All, We have used sling:resourceType="cq/gui/components/authoring/dialog/fileupload" have in our AEM components along with enableNextGenDynamicMedia as “true” to connect to Remote DAM instances. Our Polaris URL for video is of the format as below - https://delivery-p123456-e98765432.adobeaemcloud.com/adobe/assets/urn:aaid:aem:a64f4a64-0af2-4991-ghg4-68542aae43e4/as/1f605fcd-xyz-Jumpstart.mp4Directly hitting on browser gives 404 - {"type": "https://aem.api.adobe.io/problems/not_found","title": "Not Found","status": 404,"detail": "Item doesn't exist"}But if I transform the URL by stripping “/as/1f605fcd-xyz-Jumpstart.mp4” and appending “/play” makes it work on the browser by loading the “Dynamic Media Video Player”.How we render it in our DOM is FED based on ReactJS takes the URL and renders the DOM as below - <div class="video-container"> <span data-component="BannerVideoModal" data-props="{ videoUrl: https://delivery-p123456-e7654321.adobeaemcloud.com/adobe/assets/ur

Hello,I'm wondering whether this is a recent change or if I've only just noticed it. Could you also clarify what happens when it is left unchecked?Thanks!  

Hello Adobe Community Team,We have access to an Adobe Journey Optimizer (AJO) sandbox environment for our organization, Xerago, and are currently facing a couple of issues while exploring the platform. Issue 1: Audience Qualification Not Working We have created audiences using segmentation rules, and the profile data appears to be available in the system. However, the audience is not populating the list of qualified profiles, even though some profiles clearly satisfy the defined segment criteria.We have verified: Profiles are ingested and visible. Segmentation logic appears to be correct. Audience creation completes successfully. Despite this, the qualified profile count remains empty or does not reflect the expected results. Issue 2: Email Configuration Not Functioning in Sandbox The Adobe support team has already completed the email channel configuration in the sandbox environment. However, we are unable to send test emails or execute email-related activities successfully. The co

I was recently setting up a webinar campaign in Marketo and noticed registration numbers looked a little higher than expected. (In an ideal scenario, I should be happy about it, but contrary to it, I was skeptical!) When I dug into the records, I found that some attendees already existed in the database. Instead of updating those records, a few were being created as new leads because the data from the webinar platform didn't consistently match.What surprised me was how normal the situation was. Nothing was broken. The integration was working. The records just looked different enough to be treated as new people.It reminded me that duplicate leads often come from everyday marketing activities rather than major system issues.Lately, I've been thinking more about preventing duplicates before they enter Marketo instead of cleaning them up later.Some teams handle this with validation rules, while others use Marketo deduplication tools to help standardize and match records earlier in the proc