Output Monitors on Failed Action Interfer with Catch Action save errors

I'm not sure if this is a bug, but it is some what unexpected.

I just noticed that after I had attached output monitors to a build process, the capturing of the build error message in Catch Actions wasn't working.

It appears that it does not matter whether the failing Action's output monitors match anything, but that it has a output capturing to a variable.  Other forms of output monitors might also need looking into / checking.

I have attached a sample project that demonstrates the behavior with two action lists, one that monitors output and doesn't store a value in the Catch Action and one that does not monitor and does store a value in the Catch Action.  I call the monitoring action list with a matching parameter that does and does not match the output.

(edit: added attachment)

Thanks,

John

test13.fbz6 (2.728 KB)

Hi John

I was able to reproduce the issue here, this build includes the fix :

https://www.finalbuilder.com/downloads/finalbuilder/630/FB630_1847.exe

The problem was that both the output monitors and errors list were being fed from the same method, but the output monitors got first bite, and they were able to alter the text. I reversed the order as the errors collection is only used for the catch action and also has no impact on the result of the action.

Thanks, that worked great.