Setting job status to Warning

[nickdollimount]

Is it possible to set the job status to Warning? Currently I'm aware of code=0 for success, but then every other code value is error. Should this be a feature request? 😀

[jhuckaby]

Yes, just set the code property to warning, as in:

echo '{ "xy":1, "code":"warning" }'

You can do the same thing for critical (which gives you a purple status color).

I will make sure this is called out in the docs.

[jhuckaby]

This is considered an "error" for things like filtering search results, or triggering actions.

To trigger an action on a warning ONLY, just select the "On Warning" condition.

I suppose I should change the drop-down menu to say "On ANY Error" for errors? Trying to brainstorm ways of making this more obvious 🤔

[nickdollimount]

Could the trigger itself be a multi-select, and have On Error be its own, just errors? Then someone could select both On Error and On Warning if they want both?

[jhuckaby]

Hmmm, I'll add this to the TODO list, but I don't think a multi-select menu would work, because "On Error" means "all" errors, including warnings. That's a very difficult thing to change, as it's deeply rooted in the core logic of the system.

I think what we probably need is to introduce a new special menu item called "On User Error" which would mean any user-defined error code that is NOT one of the built-in ones (i.e. not warning, critical, or abort).

Let me put some thought to this 🤔

[nickdollimount]

Whatever works best for you. Now that I understand how it all is meant to work, I'm not too fussed.