When Multiple Processes (Issues) are Started by “Timer Start Event”, Login may not be Possible

This bug has been fixed.

Fixed Version

  • Version 11.3.4

Affected Version and Operation

  • Version 3.0 and later
  • Multiple Starts by “Timer Start Event” and Process Start by user operation are performed at the same time, etc.

Bug Details

  • Occurs in operating
    • A large number of Processes (Issues) were started at the same time in a specific Business Process
  • What will occur
    • Start processing does not proceed, eventually making the system unavailable
    • An error appears on the screen before logging in and you can not log in.

Workaround ・ Recovery

  • Customers using SaaS Edition
    • If this problem occurs, you can not recover it yourself. Please contact Questetra customer service.
    • By taking one of the following measures, this problem can be avoided
      • Measure 1
        • Do not use “Timer Start Event (Start type: multiple)”
          • Regarding Start type “multiple (Start number specified)”, you can substitute by placing multiple “single” ones.
      • Measure 2
        • Do not use “Message Start Event (Email)”
        • Change the starting time of “Timer Start Event (Start type: multiple)” to the time zone in which the users do not log in. (Nobody to Starts new Process)
          • if it is difficult to stop using “Message Start Event (Email)”, reduce the namber of Start in “Timer Start Event”. It is also effective to divide it into multiple “Timer Start Event” to reduce the number of Process Start per Event.
  • Customers using other than SaaS Edition
    • If this problem occurs, restart the application server to restore it.
    • This trouble can be avoided by taking the following countermeasure
      • Change the starting time of “Timer Start Event (Start type: multiple)” to the time zone in which the users do not log in. (Nobody to Starts new Process)
      • When [Start] Process, do not use [Start Selected Process] button which can start multiple items at the same time.
  • This bug is scheduled to be fixed in the next releasing version.