IncidentHandler is triggered on ExternalTask completion even if retries are set to 0

XMLWordPrintable

    • Type: Feature Request
    • Resolution: Incomplete
    • Priority: L3 - Default
    • None
    • Affects Version/s: 7.6.0
    • Component/s: engine
    • None

      AT

      • given
        • externalTask with 0 retries
      • when
        • task is completed
      • then
        • incident handlers are triggered

      Notes

      We are currently facing the following problem: the incident handlers 'resolveIncident' method (for external task failures) is invoked when calling the externalTaskService.handleFailure(...) or setRetries(...) methods, but it seems that it isn't when calling the complete(...) method for an ExternalTask. In our environment that can happen due to the nature of involved systems: we want to successfully complete an external task even though it has 0 retries and an incident.

      As the incident object itself is removed, but the incident handler is not invoked, I assume that this is a bug. I have written a failing test case here:

      https://github.com/wdw-camunda/camunda-untittesting/blob/master/src/test/java/de/wdwelab/camunda/unittesting/incidenthandler/IncidentHandlerTest.java#L77

            Assignee:
            Unassigned
            Reporter:
            Martin Schimak
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: