When deploying to an environment, we are seeing a parent process step fail overall but its child steps show as successful. The error we are seeing is:
“The step failed with error ‘An error occurred when sending a request to ‘hostname’, after the request began: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host’.”
If the release is re-deployed, the process step that failed will succeed, but then another down the line will fail with the same error.
Are there any thoughts as to why this is failing in this way? I found an old forum post that looked very similar but dealt with an “acquire package” step (which this one is not, they are all run script steps).
