Hi, I have republished on CDT, while impact anlysis, it is taking to long, norma

Impact Analysis can be resource intensive and a long process if the number of applications (under the Applications tab) and their sizes are big. In your case what seems to be happening is that the analysis completes on the server side but since it takes longer than what the client side is expecting the connection on the client times out and doesn't receive what for simplicity we can call the completion acknowledgement from the server.

In this case what you need to do is to delete all unnecessary applications to leave only the ones that are really exposing functionality in the environments; packages used just to move items from one environment to another should be deleted after the import completes to keep Impact Analysis efficient.

The workaround mention in the second comment is actually based on the real behind the scenes of Impact Analysis. Impact Analysis doesn't nothing special but scanning the applications for items to be updated and once you hit "Update" a dry export then an import is performed. The workaround described in this other comment mimics this same approach; IN THE SAME ENVIRONMENT you export whatever objects you want to update and then you import them. This updates the references with the only withdraw that you have to know what items you want to update.

Impact Analysis can be resource intensive and a long process if the number of applications (under the Applications tab) and their sizes are big. In your case what seems to be happening is that the analysis completes on the server side but since it takes longer than what the client side is expecting the connection on the client times out and doesn't receive what for simplicity we can call the completion acknowledgement from the server.

In this case what you need to do is to delete all unnecessary applications to leave only the ones that are really exposing functionality in the environments; packages used just to move items from one environment to another should be deleted after the import completes to keep Impact Analysis efficient.

The workaround mention in the second comment is actually based on the real behind the scenes of Impact Analysis. Impact Analysis doesn't nothing special but scanning the applications for items to be updated and once you hit "Update" a dry export then an import is performed. The workaround described in this other comment mimics this same approach; IN THE SAME ENVIRONMENT you export whatever objects you want to update and then you import them. This updates the references with the only withdraw that you have to know what items you want to update.