[Feature request] Specify failure context to tasks "on check failure"

[P6g9YHK6]

Is your feature request related to a problem? Please describe.

Currently, it is impossible to have tasks run on specific conditions when a check fails, which could have consequences. For example, a check failure due to a timeout or a runtime error in PowerShell might trigger unwanted task execution.

In my example, I have two scripts:

1. Check ESET status
2. Fix borked ESET

That would result in two cases that goes from inconvenient to outright unwanted

1. I cannot set the Fix borked ESET task to run only when the ESET status check detects that ESET is broken in a way that requires the fix script. This would require creating a specific check called Detect when ESET is borked.
2. Even with a Detect when ESET is borked check, there are edge cases that would trigger unwanted tasks runs:
   • When the check times out (exit 98)
   • When the check encounters a runtime error (exit 1 or else)
   • When a minor divinity of a minor cult woke up on the wrong side of the bed
   • System.OutOfMemoryException
   • etc etc

Describe the solution you'd like

The ability to specify exit codes on which to run tasks to avoid unwanted behavior and help prevent duplication of checks

Describe alternatives you've considered

Having to adapt the tasks to check that the failure was relevant

Additional context