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

With a compacted execution tree and an async task, triggering a non-interrupting event subprocess makes async job inconsistent

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.3.0, 7.2.4, 7.3.0-alpha3
    • None
    • engine
    • None

      Problem:
      Assume a one task process with a non-interrupting event subprocess. The one task is async.

      Before triggering the event subprocess, the execution tree is

      A

      After triggering the event subprocess, the execution tree is

      B => A <= C

      where B is responsible for the event subprocess and C has replaced A in executing the one task.

      Before triggering, the async job is assigned to A.

      Expected behavior:
      After triggering, the job is assigned to C.

      Current behavior:
      The job remains at A and cannot be executed successfully.

        This is the controller panel for Smart Panels app

              meyer Daniel Meyer
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: