-
Feature Request
-
Resolution: Incomplete
-
L3 - Default
-
None
-
7.6.0
-
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:
This is the controller panel for Smart Panels app
IncidentHandler is triggered on ExternalTask completion even if retries are set to 0
-
Feature Request
-
Resolution: Incomplete
-
L3 - Default
-
None
-
7.6.0
-
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: