Debugging: catch exceptions and name pattern when in batch mode

[matentzn]

Currently when dealing with dozens or hundreds of patterns, its impossible to figure out which pattern causes the issue when something fails, for example like this:

The only thing I can do is binary search (deleting patterns until I find the one causing the issue), but that costs a lot of time. Can we, in batch mode, catch any exceptions and inform the user which pattern is at fault?