Newly added service task not executed after using SetProcessDefinitionVersionCmd

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.2.0, 7.2.0-alpha4
    • Affects Version/s: None
    • Component/s: engine
    • None

      When using SetProcessDefinitionVersionCmd from within a service task, and the new process definition contains an additional service task immediately following the migration point, this additional service task is not executed. It seems the transitions of the current activity are cached.

      Example process, v1

      o - [migrate] - o

      Process v2:

      o - [migrate] - [second task] - o

      A failing unit test is available at https://github.com/jhorstmann/camunda-engine-unittest/tree/set-process-definition-version-clear-cached-activity

      I opened a pull request with a bugfix at https://github.com/camunda/camunda-bpm-platform/pull/88

            Assignee:
            Thorben Lindhauer
            Reporter:
            Jörn Horstmann
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: