When DynamicConnection Fails, Package Succeeds but Job Fails

Hi experts,
I have a 2014 package that cycles thru several MSSQL instances to collect some information. In the SSIS package,I added a Failure Constraint to insert a row to a table if the connection to that instance fails.
That works well when I run the package in Visual Studio and the package completes successfully.
BUT, when I run the Agent Job to execute the package, it Fails because a few instances could not be reached.
I don't want the job to fail in that case. How can I enable the job to reflect a Successful completion?

Can I avoid the problem above by using a Proxy Account?