Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-10199

A process instance after being aborted the current node (async) remains in RED

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Console
    • None
    • False
    • None
    • False
    • NEW
    • NEW
    • ---
    • ---

      A customer created a process instance and then they aborted it using the Rest API:
      /server/containers/{containerId}/processes/instances/{processInstanceId}
       
      They found that for the same application, one bpmn flow is working as expected (current node ) and the other bpmn flow is displayed as a stuck node with RED color and the process instance with an "aborted" stage. They're suspecting that the issue is reproducible on the flows which have an async event node.

        1. Captura desde 2024-01-16 14-25-26.png
          7 kB
          Alberto Fanjul Alonso
        2. Captura desde 2024-01-16 14-39-28.png
          8 kB
          Alberto Fanjul Alonso
        3. Captura desde 2024-01-16 14-25-26-1.png
          7 kB
          Alberto Fanjul Alonso
        4. Captura desde 2024-01-16 14-43-27.png
          7 kB
          Alberto Fanjul Alonso

            nmirasch@redhat.com Neus Miras Chueca
            nmirasch@redhat.com Neus Miras Chueca
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: