Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-8191

Cannot Use Boundary Error Event In Conjunction with a Catch All Exception Subprocess


    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 1.31.0.Final
    • None
    • Core Engine
    • None
    • 2022 Week 44-46 (from Oct 31)


      We want to handle specific business exceptions via boundary error events and any other exceptions not managed via the boundary error events to be caught by the catch all sub process.

      Posted in the google groups about this issue, the reply indicated this scenario should work and was asked to provide a reproducer - https://groups.google.com/g/kogito-development/c/DxOW164h5TE 

      Attaching reproducer. It is a Quarkus based Kogito project. Start the application and after 5 seconds workflow will start, it will enter “Node”, the node throws a “NodeException” which should be caught by the boundary error event and the “Handle Node Exception” should be invoked, instead catch all subprocess is initiated. If you remove the catch all sub process the boundary error works as expected.

      Can you please investigate on this and in the meanwhile do you know of any workarounds for this issue?

            ftirados Francisco Javier Tirado Sarti
            geoffbolton Geoff Bolton (Inactive)
            0 Vote for this issue
            2 Start watching this issue