The attached job writes "ok" to stderr, and has Output/Variable error handling set to Raise error 77777 If error output String Not equal (!=) ok. Yet it fails. Also fails if the comparison is changed to Equal (=). Also fails if the script writes something other than "ok". Just always fails.

However, it works properly if the Output/Variable error handling is set to Do not raise error 77777 If error output String Equal (=) ok: that is, it succeeds if the script writes "ok" and fails if the script writes something else.

The problem is occurring in 8.0.2. This job (or rather, a more complex one with the same error handling test) worked fine under 8.0.1.

  Jobs.txt (10kb) downloaded 62 time(s).

Can you please export the Job through File->Export?

---

You mean File => Export settings? That's how I generated the Jobs.txt file that is attached to the post. (I had to rename it from Jobs.xml because xml is not an allowed attachment type.) If I need to do something else, please send as precise instructions as you can. Thanks much.

Please test this version: http://www.visualcron.co....aspx?g=posts&t=5506 

Now, by default we do not raise errors if error output contains errors. This can now be controlled by new "On error" setting in On errors tab.

---

I have tested 8.0.3, and it appears to fix this problem.

However, I wish to reiterate that the original problem I reported in http://www.visualcron.co....aspx?g=posts&t=5448  has not been fixed. I reported there that PowerShell tasks succeed even if the script exits non-zero. A reply was posted, claiming this was fixed in 8.0.2. I tested it, and replied that the problem had not in fact been fixed.

It appears that what was done instead was to make PowerShell tasks fail if stderr is not empty. Now you have made that optional. So far so good.

But I really think that the exit status of the script needs to be checked. There is an option to check for "Non zero exit code" in the PowerShell On error... but it doesn't work.