AEM scheduled page and asset publication: including related content and preventing scope or performance issues
Scheduled (Activate Later) publication in AEM can miss related assets, pull in large numbers of unrelated items, or leave you unable to control exactly what gets published. This happens when publication runs through custom workflow buttons, OnTime node properties, or unquoted asset references instead of Manage Publication, since AEM only detects references enclosed in quotes and only Manage Publication exposes include and exclude control over the scope. OnTime and OffTime settings don’t cascade to referenced assets, and multi-resource workflows bundle everything into one package, which inflates the visible payload. Using Manage Publication with the Scope step to review and adjust references — and letting it trigger the Content Tree Publish Workflow for large batches — produces accurate, predictable scheduled publication.
Description description
Environments:
- Adobe Experience Manager as a Cloud Service
- Adobe Experience Manager 6.5 (on-premises)
- AEM Sites and Assets consoles
- Manage Publication and the Content Tree Publish Workflow
Issue/Symptoms:
- Asset references don’t appear under Published References or aren’t included in a scheduled publish, such as an unquoted raw CSS reference like
url(/content/dam/...png). - Scheduled publication (Activate Later) includes large numbers of assets or unrelated items, showing a long list of URLs in the generated-package payload.
- Custom Start Workflow buttons auto-include assets with no way to deselect them.
- OnTime node properties don’t cascade to referenced assets.
- Large bulk publication raises performance and delay concerns.
Root cause:
AEM auto-detects referenced assets using specific parsing rules — a reference must be enclosed in single or double quotes to be detected. Custom workflow triggers bypass the Manage Publication UI, which is the only standard feature that gives explicit include and exclude control. OnTime and OffTime settings don’t cascade to referenced assets, and multi-resource workflow support bundles all related content into a single generated package, which inflates payload visibility. Large publication batches need the Content Tree Publish Workflow for efficient processing in AEM as a Cloud Service.
How to confirm
- Check which publication method is in use: Manage Publication in the Touch UI, or a custom Start Workflow button. A custom Start Workflow button doesn’t support scoped publication selection.
- Confirm reference detection. In the Sites console, select the page and open Published References to see whether the expected assets are listed. If an asset is missing, inspect any custom HTML, raw HTML, or CSS for
/content/dam/...paths that aren’t enclosed in single or double quotes.
Resolution resolution
Follow these steps to resolve the issue:
- Switch scheduled publication to Manage Publication. In the Sites or Assets console, select the content and choose Manage Publication, then Publish, then Scheduling, then Later. The Scope step shows a checkbox for each related asset along with the date and time options.
- Fix asset reference detection. Enclose every
/content/dam/...path in custom HTML or CSS in single or double quotes, then confirm the asset appears under Published References. - Control what gets published. In Manage Publication, open the Scope step and deselect any references you don’t want to publish. Review the list of included items before you select Publish Later.
- Use the Content Tree Publish Workflow for large batches. When scheduling 100 or more pages, use Manage Publication, which triggers the Content Tree Publish Workflow automatically in AEM as a Cloud Service. If large delays occur, reduce the payload size per scheduled batch.
- Avoid OnTime and OffTime for coordinated publication. OnTime doesn’t cascade to referenced assets, so use Later scheduling in Manage Publication instead.
- Confirm the result. Before scheduling, check that all intended references appear under Published References, and after the scheduled time, check the Publish instance to confirm only the intended assets were published.
If the issue persists
Contact Adobe Support with a screenshot of the Manage Publication Scope step, the HTML or CSS snippet containing the asset references, the workflow model name used, and the URL of the page or asset.