Data Pipeline Copy Data Failure but still writes to Sink/Destination

[ghua]

In one of our dev data pipelines, the conenction to a source was unable to be established.  The expected result is for this to stop the job and report the failure.   The Copy action failed, as expected as it did not have access to the source.  Unfortunately, the copy action also continured to run and overwrote data in the sink/destination table with blanks as it could not retrieve data from the source. 

Data Pipeline - Copy actions should not be able to continue running after it is unable to establish a connection with the source.