I've not used the Ping task before and I'm trying to get the Task to not raise an error because the ping timed out. I've tried all kinds of combinations, including trying to make the task not raise an error for anything, and no matter what I do, the Task raises an error:

Well, I got what I wanted by enabling normal errors and then setting the Output/Variable error handling as such:



But I still do not understand why disabling all errors does not work.

In your screenshot it is set to raise errors in all cases but when the output is exactly "Request Timed Out". Is that really the case that it is exactly that string?

---

Yes, when the Ping task fails due to the machine being offline (in this case), the error output is "Request Timed Out".

I lied. We have all tasks configured to send an email on error. This task is still generating that email:

Computer: WSUSDC01
Date/Time: 2018-08-09T07:23:36
Job: Monitor Server Online - SERVER07
Task: Ping
Executed at: 8/9/2018 7:23 AM
Job Error: Success
Job ID: 6f62c30d-95c7-455d-8724-69631266220a
Task Error: Request Timed Out
Parameters (For HTTP Tasks): (No match on Variable: TASK(PrevTask|Parameters) for this task type)

Even though, the Task itself is showing a Request Timed Out, but not an error raised:

Still an issue for us, still no good answer as to why disabling all errors on Ping Tasks does not work.

I lied. We have all tasks configured to send an email on error. This task is still generating that email:

Computer: WSUSDC01
Date/Time: 2018-08-09T07:23:36
Job: Monitor Server Online - SERVER07
Task: Ping
Executed at: 8/9/2018 7:23 AM
Job Error: Success
Job ID: 6f62c30d-95c7-455d-8724-69631266220a
Task Error: Request Timed Out mcdvoice 
Parameters (For HTTP Tasks): (No match on Variable: TASK(PrevTask|Parameters) for this task type)

Even though, the Task itself is showing a Request Timed Out, but not an error raised:

In your screenshot it is set to raise errors in all cases but when the output is exactly "Request Timed Out".

In your screenshot it is set to raise errors in all cases but when the output is exactly "Request Timed Out".

If you look at my original post, I had all errors disabled. Anyway, the issue has been fixed in beta, as an additional "error" option was added for ping failed and with that unchecked, behavior is as expected.