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)