AEM as a Cloud Service Deployment Failing – "Update services" Step | Community
Skip to main content
S
sai_charanAr
New Participant
April 4, 2025
Solved

AEM as a Cloud Service Deployment Failing – "Update services" Step

  • April 4, 2025
  • 2 replies
  • 1318 views

Hi Community,

I'm encountering an issue while deploying to AEM as a Cloud Service. The deployment fails at the "Update services" step, and the error message states:
"The deployment failed due to a system issue. Contact Adobe Support if the issue recurs."

Here’s what I’ve observed so far:

  • Update Indexes → Finished

  • Build Transform → Finished

  • Update services → Failed

  • Install mutable content → Running

Has anyone else faced this issue? What are some potential troubleshooting steps I can try before reaching out to Adobe Support? Any insights would be greatly appreciated!

Thanks!

Best answer by narendiran_ravi

Hi @sai_charanar ,

Raising a support ticket is recommended for these issues. However, you can try the following steps on your end:

  1. Download the pipeline logs
    Check if there are any errors logged that might indicate the root cause.

  2. Re-run the pipeline
    Sometimes the issue could be due to cloud services in AEMaaCS.

  3. Run the pipeline with the previous build
    This helps determine if the issue is related to recent code changes.

  4. Check the distribution queue on the author tier
    Ensure the queue is not blocked, as this can prevent successful deployments.

2 replies

kautuk_sahni
kautuk_sahni
Employee
April 14, 2025

@sai_charanar Did you find the suggestions helpful? If you need more information, please let us know. If a response resolved your issue, kindly mark it as correct to help others in the future. Alternatively, if you discovered a solution on your own, we'd appreciate it if you could share it with the community. Thank you!

Kautuk Sahni
narendiran_ravi
narendiran_raviAccepted solution
New Participant
April 4, 2025

Hi @sai_charanar ,

Raising a support ticket is recommended for these issues. However, you can try the following steps on your end:

  1. Download the pipeline logs
    Check if there are any errors logged that might indicate the root cause.

  2. Re-run the pipeline
    Sometimes the issue could be due to cloud services in AEMaaCS.

  3. Run the pipeline with the previous build
    This helps determine if the issue is related to recent code changes.

  4. Check the distribution queue on the author tier
    Ensure the queue is not blocked, as this can prevent successful deployments.

Terms & ConditionsAccessibility statement

Loading footer...