I've been trying to find a way to reset a process error status when a normal and expected condition occurs that IPA treats as an error. The current issue is testing if a file exists.
The File Access node can do that, but if it detects the file does not exist, it treats it as an error condition. In this case, the file is probably present in 15% of the runs, and it is a normal condition for it not to exist. If it's not found, the process does some housekeeping and terminates normally, but IPA flags the work unit as having errored, even if several subsequent nodes that include error handling do not encounter an error.
I also tried a System Command node with a Windows command file that uses IF NOT EXIST to test the file, but the only way to pass that fact back to the process is via errorlevel which, as might be expected, sets an error condition in the process.
I looked into forcing it with an Assign node, but system variables are not available for assignment.
Right now, the only downside to this behavior is that errors appear in the work unit log and the work unit is displayed in red in the administrator, but it's not hard to envision a time when some kind of automated error test process might be developed to check for work unit errors, in which case this would be a false positive.
Any ideas on how one might reset the error condition?
I don't see that checkbox, is it on the General tab of Properties?
Maybe it's in a later version of IPD...I'm on 10.0.6.12..6247 until we upgrade our Landmark server.
That could be the problem. Bummer. I'm using 10.1.1.19.4412. Here's a screenshot: