elai-shalev opened a new issue, #2094:
URL: https://github.com/apache/incubator-kie-issues/issues/2094

   In a setup that includes a parent workflow that dispatches subflows, when a 
subflow is in ERROR state, the parent workflow is stuck on ACTIVE state 
forever. 
   Even though the subflow is registered in the Data Index, the parent workflow 
never finishes. The parent workflow gets stuck on the node that has dispatched 
the subflow, and the error is not propagated. 
   
   I consider this a bug because the unexpected error should propagate up to 
the parent flow and cause it to fail. The parent flow should not run 
indefinitely — it should either proceed to the next steps or terminate with an 
error, but in any case, it should reach a proper completion.
   
   Please take a look at this [reproducer 
workflow](https://github.com/elai-shalev/orchestrator-demo/tree/subflow-err-pass-reproducer/0x_subflows/subflow)
 for the issue. 
   
   And please also view the Graphql query result from the Data Index  of the 
states:
   ```      {
           "processId": "parent",
           "processName": "Parent",
           "state": "ACTIVE",
           "start": "2025-09-10T11:42:59.27Z",
           "businessKey": null,
           "error": null
         },
         {
           "processId": "fail",
           "processName": "Fail",
           "state": "ERROR",
           "start": "2025-09-10T11:42:59.268Z",
           "businessKey": null,
           "error": {
             "message": "java.lang.NullPointerException - RESTEASY004690: 
Parameter annotated with PathParam cannot be null"
           }
         },
         {
           "processId": "pass",
           "processName": "Pass",
           "state": "COMPLETED",
           "start": "2025-09-10T11:42:47.249Z",
           "businessKey": null,
           "error": null
         }
       ]
     }
   }
   ```
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to