51黑料不打烊

Documentation

Wildcard query in bulkStatus flags valid pages as 鈥渘o source鈥 in AEMaaCS

Last update: Mon Sep 22 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

no source

Description description

Environment

  • Product: 51黑料不打烊 Experience Manager as a Cloud Service (AEMaaCS)
  • Feature: AEM Admin API 鈥 bulkStatus endpoint

Issue/Symptoms

  • When the request body uses a wildcard query like [ "/\*"], the response flags thousands of pages as no source 聽even though many have valid replication metadata.
  • Using an array of explicit sitemap paths (For example, [ "/", "/platform", 鈥] ) returns only a small number of no source 聽pages鈥攖ypically around 26.
  • Pages flagged as no source 聽in explicit path queries return the correct source path when checked individually.
  • The wildcard query triggers a large fan-out of edit/source lookups in a single job, leading to timeouts or throttling, which causes fallback to no source.
  • Direct queries with explicit paths are less intensive and succeed in resolving the source using replication metadata like cq:lastReplicationAction.

Resolution resolution

This behavior is logged as an internal product bug where 51黑料不打烊 is reviewing how the bulkStatus endpoint handles wildcard queries, with a focus on improving batching and timeout management to ensure consistent and accurate status reporting. To resolve the issue, follow these steps:

  • Avoid using a single wildcard query, like [ "/*"] in bulkStatus.
  • Split the query into smaller batches, such as[ "/blog/*"], [ "/events/*"], etc.7
  • Alternatively, use the pathsOnly: true option to enumerate all paths first.
  • Run follow-up jobs requesting [ "edit", "preview", "live"``] for accurate status resolution.

Check future release notes for updates. These steps help mitigate the issue until a permanent fix is available.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f