AEM Sites Playbook, Chapter 10: Preview, publication, scheduling and withdrawal
How do we release and remove the complete approved experience?
November 10, 2026
Define the intended release
Use this chapter when releasing or removing content, especially when pages contain shared fragments, media, tags or locale references. Identify the approved revision, affected audience, destination, deadline, dependency set and accountable publisher. A release record should let another operator determine what was supposed to happen without reconstructing a chat conversation.
Differentiate saved content, approval, completed processing, Preview availability, publication and customer-visible delivery. Each is an observation with its own evidence. Adobe's authoring/publication concepts establish the tier distinction. Use the Cloud Service publication guidance or 6.5 publication guidance for the target installation rather than combining their procedures.
Build the scope before publishing
Start from the page or structured content being changed. Inspect required references, shared dependencies, children and translated variants. Determine which changes are approved and whether publishing a shared dependency affects other experiences. Make that consequence visible to the approver.
The 6.5.14 fragment-workflow question concerns a fragment publishing while images or tags remained absent. The suggested custom handling lacks author-confirmed success. Treat it as a dependency test case: verify the actual workflow on a fixture containing the reference types your project uses.
For a hypothetical localized campaign, the scope might include a page, a shared image and a translated Experience Fragment. Verify the page in its delivery context, including navigation and destination links. If Preview is part of the process, reviewers should confirm the complete experience there and record any difference from production delivery.
Rehearse the release sequence
Approve the complete scope
Resolve pages, references, assets and scheduled time.
Observe the intended route
Verify the approved revision with the target identity.
Prove removal or replacement
Check caches, search and connected consumers.
Step 1. Confirm the approved content/code versions and that required processing has finished.
Step 2. Resolve the dependency set and approval scope, then use the supported publication operation.
Step 3. Inspect the operation's result and any queued or failed items.
Step 4. Retrieve the intended delivered URL/API response using the target identity and record the content revision and time.
Step 5. Compare the observed result with the agreed deadline and acceptance criteria.
For scheduled operations, record the business time zone, configured schedule and operator responsible for observing execution. Test a representative scheduled change before relying on it for a launch window. Include cancellation and a missed/failed execution in the operating procedure.
Distinguish evidence of each release state
Community discussions show why publication evidence must include dependencies and delivered output. In the AEM 6.5.14 example, custom reference handling remains unconfirmed; the Cloud Service example leaves the delivered symptom unresolved. A proposed code change or one status property does not prove that the approved experience reached its audience.
Scroll horizontally if needed.
| State | Evidence it provides | What still needs checking |
|---|---|---|
| Saved | The author stored a proposed state | Approval, dependencies and intended audience |
| Approved | A defined revision/scope has an authorized decision | Processing and publication operation |
| Processed | Required outputs exist for the dependency | Correct references and destination |
| Previewed | Reviewers observed a configured preview experience | Production-specific routing/access and publication |
| Published | The supported publication operation reports its result | Actual response, locale, identity and cache freshness |
| Withdrawn | The chosen removal operation ran | Remaining references, public routes, search and external consumers |
Keep operation time and observation time separately. A launch requirement concerns the result the audience must receive; the team needs evidence connecting that result to its operation.
Worked scenario of a scheduled bilingual launch
This hypothetical campaign includes two locale pages, a shared fragment and an image. The business owner requires a coordinated launch window and a controlled withdrawal afterward. A regional reviewer must accept each locale, and the operator must know who can authorize a partial launch.
The release owner creates a dependency record before scheduling:
Scroll horizontally if needed.
| Item | Required condition | Owner |
|---|---|---|
| Locale pages | Approved revision and correct local references | Regional content owners |
| Shared fragment | Approved content with understood dependent scope | Shared-content owner |
| Image | Required processing/output and intended destination | Media owner |
| Schedule | Agreed business time zone, configured time and execution observer | Release owner |
| Customer routes | Intended domain, locale, identity and content revision | Delivery/channel owners |
| Withdrawal | Replacement/removal policy and verification window | Business/release owners |
The operator rehearses approval, dependency processing, preview where applicable, scheduling, observation and cancellation on representative fixtures. The team also tests a deliberately failed dependency and an unavailable observer. It chooses an escalation response before the real window.
Suppose the rehearsal shows the first locale complete, the second referencing the wrong fragment, and the image present only in Preview. The scheduling operation itself succeeds. The result is still a hold for the coordinated launch because the approved dependency set has not reached the intended destinations.
The content owner may request a narrower launch only by explicitly accepting its audience, locale and communication implications. The operator does not make that business decision merely because one page is ready.
Select the recovery that matches the failure
Scroll horizontally if needed.
| Observation | Candidate response | Verification |
|---|---|---|
| One known item failed publication | Correct the known cause and retry the supported operation | Intended item/revision is delivered |
| Dependency was not approved | Return it to the correct decision state | Approval scope and subsequent publication are explicit |
| Processing output is missing | Repair the processing handoff | Required output exists before publication |
| Public response is stale | Follow the actual delivery/cache diagnosis | Correct revision appears under the agreed route/identity |
| Wrong content was released | Use the authorized correction/withdrawal/recovery path | Customer result and affected dependencies are verified |
| Schedule was misunderstood | Inspect time zone, configured event and actual execution | Rehearsed scheduling policy, not repeated blind scheduling |
Use the appropriate Cloud Service or 6.5 publication procedure. Do not treat them as a combined menu or assume custom workflows collect every required reference.
Make withdrawal part of launch readiness
Before publishing, identify what the customer should see after expiry: a replacement, redirect, unavailable result or retained archive. Test the chosen behavior through the same domain and identity used for launch. Check references and downstream consumers, not just the original page URL.
In the hypothetical rehearsal, a withdrawn page could disappear while its shared fragment remains available through another approved consumer. That may be correct or incorrect depending on scope. Record the business intent before deciding which content to remove. Conversely, a successful removal job with an old cached response has not met an immediate withdrawal requirement.
The release is ready when an operator can state the approved scope, perform the intended operation, observe the required result and handle each agreed failure condition. Keep the evidence with named owners so the next scheduled update does not depend on reconstructing the first launch from memory.
Prove withdrawal as well as launch
Decide whether a withdrawn page should disappear, redirect, show a replacement or remain in an approved archive. Include cached content, search results, references and external consumers in the verification. A repository or replication-status indicator is not proof of the visitor's result; the Cloud Service navigation-filtering discussion illustrates that distinction without a final confirmed repair.
If a release fails, assign the smallest appropriate recovery: retry a known failed operation, restore approved content, fix a dependency or reverse a code/configuration change. Do not repeatedly republish a broad tree without identifying what is wrong.
Complete W10 with approval, dependencies, processing, destination, operation result, public observation and withdrawal behavior. The content owner accepts the experience, the release owner confirms the operation and the delivery owner supplies freshness evidence from chapter 11. Keep exceptions explicit; a deadline should not silently remove a mandatory dependency check.
W10 Publication and withdrawal evidence
Use with chapter 10. Record the visitor-facing observation as well as the job result.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Approved revision/code and dependency set | [enter] |
| Processing complete, scope approved and Preview result where applicable | [enter] |
| Destination, operation, schedule/business time zone and execution owner | [enter] |
| Operation result, failed items and queue state | [enter] |
| Delivered URL/API, identity, revision, time and deadline result | [enter] |
| Withdrawal behavior, observation and recovery/exception owner | [enter] |
