Issue Summary

After transferring the repository to the new workspace and deleting (or de-activating) the old workspace, the deployment is no longer working.

Error message : 

"error": { "message": "Not found", "detail": "Response Summary: HttpResponseSummary{httpStatusCode=404, httpStatusMessage=Not Found, bodyAsString={\"key\":\"account-service.account.not-found\",\"message\":\"Response Summary: HttpResponseSummary{httpStatusCode=404, httpStatusMessage=Not Found, bodyAsString={\\\"key\\\":\\\"account-service.account.not-found\\\",\\\"message\\\":\\\"Account {eXXXXXec-7XXa-4XXe-aXX5-5XXXXX5}does not exist.\\\",\\\"arguments\\\":Unknown macro: {\"uuid\"}}} (command DEPLOY_SERVICE_ACQUIRE_ENVIRONMENT_LOCK, error key='account-service.account.not-found')", "data": { "key": "account-service.account.not-found", "arguments": { "uuid": "{eXXXXXec-7XXa-4XXe-aXX5-5XXXXX5}"  

Steps to Reproduce

• Enable repository pipelines for deployments.
• Run the pipelines and complete the deployment.
• Transfer the repository to the new workspace.
• Delete the old workspace (wait for 30 days for data to totally removed from the database)
• Run the pipelines again.
• The deploy button will not work, shows the above error in the HAR: 

Expected Results

The deployment should proceed without encountering any issues.

Workaround

First, delete the affected deployment environments from the deployment settings. After that, recreate them. If this doesn’t solve the problem, try running the entire pipeline again after you’ve recreated the deployment environment.