AEM Assets stuck in Processing: restore authoring without guessing at publication

A campaign asset can upload successfully yet remain unusable. In AEM as a Cloud Service, authors may see a permanent Processing state and no asset in the content finder. Adobe's August 2026 knowledge article names that symptom and describes a recovery path for an issue addressed in later maintenance updates. The failure affects the authoring handoff even before anyone asks whether the asset has been published.

Establish the failure boundary

Collect a small sample: upload time, asset path, file type, size, processing status, author environment and whether sibling uploads succeed. Check the relevant processing logs and service health. If only one file fails, investigate that file and its metadata. If many unrelated assets stop at the same step after an environment change, treat it as a platform incident.

Confirm the content finder symptom with the same author role and page editor context that reported it. A user can have asset permission or search-scope trouble that looks similar to a processing failure. Do not mix those causes into a single “assets missing” ticket.

Recover in a controlled order

First confirm the environment's maintenance release and whether Adobe's documented issue applies. Adobe's article recommends an Author service restart and reprocessing affected assets when they are stuck. Schedule that restart through the team's incident process, with an owner, impact window and rollback or escalation route. Do not use a restart as the first response to every missing asset.

After the service is healthy, reprocess the affected assets from the Assets console. Monitor them until they reach Processed, then open representative assets and confirm renditions and metadata needed by the site. Recheck the content finder in the page editor. If status or availability still fails, preserve logs and engage Adobe Support rather than repeating disruptive restarts.

Make authoring and publishing separate gates

“Processed” means an asset is ready for the next workflow stage; it does not prove that the page references the right asset, that permissions allow the author to use it, or that the published site serves the expected rendition. Keep a short acceptance set for each campaign: asset available to author, page reference saved, publication completed, live route checked.

Adovo’s view

An asset pipeline has two customers: the machine that processes files and the author who must use them. Green service status means little when the content finder is empty. Recover the processing path, then prove the handoff in the editor. The incident closes when the campaign can move, not when a background job turns green.