I have the same problem. It was supposed to “finish” the image subprocess. What happened until last week, and now it stopped working. This close connection is not actually bringing down the connection.
The CloseConnection property is ignored if the OutputConnection property is set. We consider that the connection is meant to be used at a later point in the workflow so we do not close it.
If the connection is not meant to be reused, do not set the OutputConnection property.
This is not explicitly documented right now but there is a new version of the terminal activities documentation in the works and it will include an explanation for this behavior.