Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issue with the Deployment Manager pipeline build



Deployment Manager dev ops pipeline is used to manage migration. User starts a build and it works fine. However, it does not work when the user stops the build.

Error Messages

Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to yourEnvironment] failed: connect timed out
org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect( ~[httpclient-jar:?]
org.apache.http.impl.conn.BasicHttpClientConnectionManager.connect( ~[httpclient-jar:?]
org.apache.http.impl.execchain.MainClientExec.establishRoute( ~[httpclient-jar:?]
org.apache.http.impl.execchain.MainClientExec.execute( ~[httpclient-jar:?]
org.apache.http.impl.execchain.ProtocolExec.execute( ~[httpclient-jar:?]
org.apache.http.impl.execchain.RetryExec.execute( ~[httpclient-jar:?]
org.apache.http.impl.execchain.RedirectExec.execute( ~[httpclient-jar:?]
org.apache.http.impl.client.InternalHttpClient.doExecute( ~[httpclient-jar:?]
org.apache.http.impl.client.CloseableHttpClient.execute( ~[httpclient-jar:?]
pega.platform.integrationcore.client.http.internal.ComponentsHttpClient.invokeHttpClient( ~[integration-core.jar:?]

228[http-apr-8080-exec-8][STANDARD][ ][sFoundation](ndler.Pega_Int_Pipeline.Action)INFO T-Task status processing completed.Task:deploy Build id:PEGA-PIPELINE-CD IS-57

Steps to Reproduce



Root Cause

A defect or configuration issue in the operating environment. The User Interface (UI) is out of sync with the data. An uncaught exception for pzPauseTask (for build ID PEGA-PIPELINE-D+IS-57) occurs. Logs indicate that a deployment with the build ID PEGA-PIPELINE-D+IS-57 is completed.


Perform the following local-change: 
  1. Contact the Global Customer Support (GCS)
  2. Request for
  3. Install and run 

Below are the steps to use

  1. Import Rule-Admin-Product (RAP) to the Deployment Manager instance
  2. Add the branch ruleset to the application rule
  3. Open the deleted deployment activity
  4. Run the activity by passing the problematic build ID (IS-57)
  5. Wait till the deletion is completed
  6. Remove the branch ruleset from the application ruleset
  7. Create a new deployment by updating the deployment name


Published August 19, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us