Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-11927

Execution Metrics for Multi Instance Tasks counts Parent and Child Executions

    • Icon: Bug Report Bug Report
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • admin, engine
    • None

      Steps to Reproduce

      • execute the attached process
      • observe the execution metrics

      Problem

      The attached process has three elements including a MI User Task with Loop Cardinality 3. When I execute the process I would expect a FNI count of 5 but observe an FNI count of 6.

      Hint

      As execution metrics tracking is implemented through ExecutionListeners, it counts parent multi instance execution plus child executions. This is why the counter is always +1 than expected. Technically correct but hard to understand from a user perspective.

        This is the controller panel for Smart Panels app

            [CAM-11927] Execution Metrics for Multi Instance Tasks counts Parent and Child Executions

            michael.schoettes, I had a discussion with thorben.lindhauer, and this is the expected behavior. An activity will be created for the "parent" scope, which contains the loop cardinality variable, as well as separate "child" activities for each separate instance. It's the same as a sub-process, there will be an FNI for all the activities in the sub-process, as well as an additional FNI for the actual sub-process instance.

            As this is expected behavior, I'm closing this ticket.

            Best,
            Nikola

            Nikola Koevski added a comment - michael.schoettes , I had a discussion with thorben.lindhauer , and this is the expected behavior. An activity will be created for the "parent" scope, which contains the loop cardinality variable, as well as separate "child" activities for each separate instance. It's the same as a sub-process, there will be an FNI for all the activities in the sub-process, as well as an additional FNI for the actual sub-process instance. As this is expected behavior, I'm closing this ticket. Best, Nikola

             

              Unassigned Unassigned
              michael.schoettes Michael Schoettes
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: