Expand my Community achievements bar.

SOLVED

RDE - Deployment Failed Status

Avatar

Level 4
Level 4

Hey guys,

 

My RDE environment in cloud manager is showing RDE as "Deployment Failed"

Cross_Leaf_0-1731577657041.png

However, the aio:aem:rde install command is not reporting any such issue,

Cross_Leaf_1-1731577748089.png


Checking the developer console it shows the pod as active -

Cross_Leaf_2-1731577883575.png


If I try to open the author or publish service I get the below -

Cross_Leaf_3-1731577936680.png

 

Any help why the discrepancy?

 

thanks,

CL

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hey @_CL,

If it's just RDE, try resetting the RDE once! It's usually good practice to reset the RDE into a default state for the next usage in case of multiple developers working at the same time.

Can you put up the logs for the build that set the status to deployment failed?

 

Hope this helps!

Rohan Garg

View solution in original post

5 Replies

Avatar

Level 5

If there is nothing in logs, I would raise a ticket to Adobe.

Avatar

Level 4
Level 4

We're using a sandbox program here and Adobe does not provide technical support for that unfortunately!

Avatar

Correct answer by
Community Advisor

Hey @_CL,

If it's just RDE, try resetting the RDE once! It's usually good practice to reset the RDE into a default state for the next usage in case of multiple developers working at the same time.

Can you put up the logs for the build that set the status to deployment failed?

 

Hope this helps!

Rohan Garg

Avatar

Level 4
Level 4

yeah that's an idea but we'd lose all the custom content packages we've deployed over past months, anyways to go about w/o resetting the instance?

Avatar

Level 5

In the past, I faced a similar issue in my sandbox environment. We had no other option but to reset the RDE. To sync the contents again, we used the content copy option. Another challenge was updating the environment variables, which we addressed using the Cloud Manager API. Specifically, we utilized the endpoint:

https://cloudmanager.adobe.io/api/program/{{programId}}/environment/{{environmentId}}/variables

This allowed us to add environment variables programmatically, avoiding the need for manual updates through the Cloud Manager UI.