Give users the option to FAIL on Content Sets Copy if a path does not exist or there is an issue instead of a warning - Status changed to: Investigating

[#1]

Request for Feature Enhancement (RFE) Summary:	There was an update a while back which changed the functionality of content sets copy  tool to continue and succeed even if there is an issue with a given path. This is not an ideal change as we rely on Content Copy statuses to do certain things like notify our users when a path fails and we are now receiving false positives. We would like the option to return the functionality to how it was before which is to give a status of fail and cancel the copy if there is an issue with the path or the path does not exist
Use-case:	Routine Content Copy
Current/Experienced Behavior:	Copy succeeds even if path does not exist
Improved/Expected Behavior:	Copy should fail if path does not exist or issue with a given path
Environment Details (AEM version/service pack, any other specifics if applicable):	AEMCS
Customer-name/Organization name:	Chipotle
Screenshot (if applicable):
Code package (if applicable):

no_fail.png ‏63 KB

[#2]

@brosenstein 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-17822. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.