Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-4803

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

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Hide
      1. Build and deploy the kjar using the attached project.
        • Note: The process contains only a human task node. 
      2. Start it through
          POST/server/containers/{containerId}/processes/{processId}/instances
      3. Abort it through 
           DELETE/server/containers/{containerId}/processes/instances/{processInstanceId}
      4. Open the diagram from business-central.

      Actual result

      You would see the human task node is still marked as RED.

      Expected result

      Human task node is highlighted as a current node - BLUE.

      Show
      Build and deploy the kjar using the attached project. Note: The process contains only a human task node.  Start it through   POST /server/containers/{containerId}/processes/{processId}/instances Abort it through     DELETE /server/containers/{containerId}/processes/instances/{processInstanceId} Open the diagram from business-central. Actual result You would see the human task node is still marked as RED. Expected result Human task node is highlighted as a current node - BLUE.
    • ---
    • ---

    Description

      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.

      Attachments

        Issue Links

          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBPM-10199 A process instance after being aborted the current node (async) remains in RED

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBPM-10215 A process instance after being aborted the current node (async) remains in RED

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              nmirasch@redhat.com Neus Miras Chueca
              rhn-support-luzrodri Luz Rodriguez
              Dominik Hanak Dominik Hanak
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: