Unexpected task execution created after failed task rerun

[Anton Kazakov]

In short, if we rerun one of two tasks linked by on-complete clause, new unexpected task execution will be created for the second task.

More detailed description:
Let's assume we have such WF definition. Tasks 1-2-3 linked with on-complete clause:

test_wf:
  type: direct
  tasks:
    t1:
      action: some_action_1
      on-complete:
        - t2
    t2:
      action: some_action_2
      on-complete:
        - t3
    t3:
      action: some_action_3
      on-success:
        - t4
    t4:
      action: some_action_4

After first execution actions some_action_2 and some_action_3 failed for some reason, so we have next workflow execution structure:
test_wf [state=ERROR]
executions:
    t1 [execution_id=t1_exec_id, state=SUCCESS]
    t2 [execution_id=t2_exec_id, state=ERROR]
    t3 [execution_id=t3_exec_id_1, state=ERROR]

So we rerun task t2 with PUT request to <mistral_url>/v2/tasks/t2_exec_id. some_action_2 and some_action_3 got completed successfully, but workflow still becomes ERROR with such execution structure (note there are two t3 executions):
test_wf [state=ERROR]
executions:
    t1 [execution_id=t1_exec_id, state=SUCCESS]
    t2 [execution_id=t2_exec_id, state=SUCCESS]
    t3 [execution_id=t3_exec_id_1, state=ERROR]
    t3 [execution_id=t3_exec_id_2, state=SUCCESS]

Looks like new t3 execution (with id=t3_exec_id_2) shouldn't have been created in this case. Instead, t3_exec_id_1 should've been rerun by Mistral.

[Renat Akhmerov (rakhmerov)]

Hi, what DB are you using?

[Anton Kazakov (ton.kazakov)]

Hi, it is PostgreSQL 10.8