This bug has been fixed.

Fixed Version

  • Ver. 12.2.0

Affected Version and Operation

  • Version 8.0.0 and later versions
  • For the operation to occur this, please see the Bug Details

Bug Details

  • May occur when any of the following processing combinations are executed at the same timing:
    • User terminates the Process/the workflow engine moves the token
    • Process ends at a Terminate End Event/the workflow engine moves the token
      • The conditional requirement is that the token has been split into multiple by [AND / OR gateway]
  • What will occur
    • Even though the Process is finished (“End” or “Terminate End”), the situation will be as follows:
      • There exists an automatic processing step (e.g. [Script Task]) that is in the state of “in processing” and whose token does not move
      • There exists a step of [Human Task] that can be operated or [Catching Message Intermediate Event (HTTP)] that is standing by
        • These can be processed and advance tokens


  • There is no way to recover if this problem occurs
  • This bug occurs about once in every hundreds of thousands of Processes (occurrence rate: 0.001% or less)
  • This Bug is due to be fixed in the coming version (Ver. 12.2.0)

1 thought on “Operable Tasks may Remain despite the Process has been Finished (Fixed)”

  1. Pingback: v12.0 2020-10-12 In [My Tasks] etc. Sorting by Title Becomes Available – Questetra Support

Comments are closed.

%d bloggers like this: