Hi Team,
Recently we are seeing an issue on pipeline execution for AEMCS.
The execution has been stuck during the deployment to the dev stage for several hours. Has anyone else faced a similar issue?
We contacted the support team during the initial occurrence. While they couldn’t identify the root cause, they mentioned that one of the pods was stopped, which they assumed might be the reason.
The issue has happened again today, but we haven’t received any feedback from the team yet. We haven’t made any customizations to the pipeline—our code builds successfully locally and has been pushed to the Adobe pipeline.
Has anyone else observed a similar problem?
Thanks,
Geo
Solved! Go to Solution.
hi @georhe6 I can confirm experiencing similar issues in the past. Contacting Adobe was the way to go.
Have you tried creating a "clone" of that pipeline and see if that goes through?
hi @georhe6 I can confirm experiencing similar issues in the past. Contacting Adobe was the way to go.
Have you tried creating a "clone" of that pipeline and see if that goes through?
Hi,
Unfortunately, this can sometimes occur. You can reach out to Adobe through their support ticket system in such scenarios.
Views
Likes
Replies