The latest version of LiveCycle contains a "bolt" to trap exceptions.
If you're using 8.2, you can try to leverage the Exception event.
Create a separate process and add a Exception event Start Point. This should catch the exception.
I didn't know the option with creating Exception event. It could be better then "bolts" approach for larger processes to avoid messy catching of multiple exceptions.
Do I understand correctly, that Exceptions for e.g. JDBC service are not hierarchical?
So that catching "SYSTEM EXCEPTION" does not catch SQLException nor JDBCConnectionException and if I want to handle all the exceptions I have to drag 5 exception-worflows?
Which approach is more commonly used - "bolts" or exception events?
You are correct. They are not hierarchical. You would need one route per exception you want to trap.