Troubleshooting long build times in Adobe Experience Manager Cloud Manager pipelines
This article provides guidance for Adobe Experience Manager Cloud Manager users who encounter unusually long durations during pipeline executions in the Build step, including steps to identify and respond to transient issues.
Description description
Environment
- Adobe Experience Manager (AEM) Cloud Manager
Issue/Symptoms
- Pipeline executions experience unusually long durations during the Build step.
- No changes to code or configuration are present.
- No specific errors appear in the build logs.
- Rerunning the pipeline without changes results in a normal build duration, suggesting that the issue is transient.
Resolution resolution
Follow the steps below to resolve the issue:
-
If you notice that a pipeline Build step is taking significantly longer than usual, do not immediately cancel the execution.
-
Allow the build to continue for a reasonable period to determine whether it completes successfully.
-
If the build is canceled or fails without any actionable error in the logs, trigger the pipeline again without making any changes.
-
Observe the duration and outcome of the subsequent execution:
- If the pipeline completes successfully and within the expected timeframe, the issue was likely a transient processing or orchestration delay. No further action is required.
- If the issue recurs or persists across multiple executions, collect the relevant build logs and details, and contact Adobe Support for further investigation.
-
Continue to monitor pipeline executions for recurring delays.
recommendation-more-help
experience-cloud-kcs-help-kbarticles