Errors with the pipeline after a clone

[Craig22]

After cloning our Prod environment to our Dev and Test instances, we are no longer able to submit our applications to the deployment pipeline and AES just throws a generic "This operation failed" while the logs indicate "Requested URI does not represent any resource: /sn_deploy_pipeline_deployment_pipeline_api/appProperties/<sys_id>: no thrown error"

I have re-validated the pipeline configuration in Prod (Validate and updated each instance) and checked the credentials are also configured correctly with appropriate roles .

Just curious if anyone has seen anything like this before or where if there is anything I should be checking beyond the above?

[Paige Duffey]

Hi Craig,

Have you confirmed that you still have the controller environment setup in your cloned instances? Each instance in your pipeline should have a environment marked as it's controller (prod, usually) along with associated credentials. I'd verify that that environment in each sub-prod instance is still setup and validate it from that subprod instance.

[Craig22]

Our Dev and Test instances both still contain a Prod environment entry with the "Is Controller" option selected.  I've validated both but no change