Engine should not throw exception when Acquired Job does not exist anymore

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.1.0, 7.1.0-alpha3
    • Affects Version/s: None
    • Component/s: engine
    • None

      Sometimes jobs are cancelled after they have been acquired but before they are actually executed:

      --> Job is acquired
      --> Job is added to Queue
      >>>> Job is deleted (interrupting boundary event or sth. comparable fired)
      --> Job is taken from Queue and attempted to be executed
      --> Process Engine throws exception

      The process engine should not throw an exception here but rather fail gracefully and ignore the acquired job.

      AT:

      • remove Exception and replace with DEBUG logging message.

        This is the controller panel for Smart Panels app

              Assignee:
              Roman Smirnov
              Reporter:
              Daniel Meyer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: