The background to this question comes from a customer where we are using the cDOT "Add CIFS Share ACL" command. As this command loops through and adds each user/group it reports errors as warnings (using Get-WfaLogger -Warn which appear as yellow text in the log) and then at the very end it checks to see if there were 'any' errors and if so, it throws an error message and the workflow aborts. Not a problem.
However, I'm considering alternatives for some possible changes to this logic (in a clone of this cmd). One could want to continue workflow execution is the error (or errors) encountered were "duplicate entry" for example (or some other specifically trapped error). But it would be nice if the command step could communicate back up to the workflow level that a warning condition occured and have WFA color that command step yellow but continue executing the rest of the workflow.
I don't believe this is possible but asking to make sure.