Hi @MatthewDa19, Is there a specific reason you’re registering your servlet using path?If you use a resourceType instead, you won’t need to expose /bin or mask it. You can leverage selectors and extensions directly on content paths. Docs for reference: https://sling.apache.org/documentation/the-slin...

Hi @MatthewDa19, You may need custom cache rules, filters, or vhosts for each tenant Since dispatcher configs are shared, the best practice is: Centralized dispatcher configuration repository: Maintain a dedicated Git repository for all dispatcher configs. Include tenant-specific configs as separ...

Hi @ArindamCh, Which version are you on AEM as a Cloud Service or AEM 6.5?Because the way to add custom Inbox actions (Reject, Archive) differs:For Cloud Inbox UI is React-based → you cannot overlay /libs/.../actions. Here is what you can do: Implement an OSGi service: @Component(service = Workfl...

Hi @NageshRaja, 1. Approach to CRUD operations on Content Fragments from Publish Directly modifying CFs on Publish is not supported/recommended in AEMaaCS. Publish instances are transient, do not persist changes across restarts, and there’s no reverse replication. The recommended approach is exact...

Hi @PriyaNair1, Can you try this? public List<Page> filterAndSortPages(List<Page> pages, Predicate<Page> filter) { if (pages == null || pages.isEmpty()) { return Collections.emptyList(); } return pages.stream() .filter(Objects::nonNull) .filter(Page::isVa...

Hi @NituDh, Looks like your AEM could not bootstrap its repository because the Oak Segment Store is corrupted. The oak-run check output confirms this: multiple SegmentNotFoundException and no valid checkpoints found, which means the repository state cannot be reconstructed normally. Here are the ste...

@PavanGaddam  Thanks for expanding on this - you’re absolutely right that under a properly configured AEMaaCS + Dispatcher + CDN setup, cache misses should always fall back to Publish and a 404 should only occur if the page truly isn’t available yet (unpublished, activation in progress, or origin is...

Hi @NamitaDu, Agree with @PavanGaddam and yes he is right it's a Fastly. this is a sequencing issue. In AEM as a Cloud Service, content activation to publish is asynchronous across all publish instances. If you trigger a Fastly purge immediately after activation, the CDN can request the new asset/pa...

Hi @NavyaVo, Yes - Adobe has officially deprecated Service Account (JWT) authentication for IMS integrations. The recommended replacement is OAuth Server-to-Server credentials. Migration steps for your reference: In Adobe Developer Console, create new OAuth Server-to-Server credentials for your AEM...

Hi @Vishal_Kagde, Looks like, your JSON payload is too minimal. Splunk HEC expects an event field plus metadata like time, host and sourcetype. Even with 200 OK, missing these can prevent indexing. Can you try this if it works: JSONObject payload = new JSONObject(); payload.put("time", System.curre...