-
Type:
Bug Report
-
Resolution: Unresolved
-
Priority:
L3 - Default
-
None
-
Affects Version/s: 7.4.x, 7.5.x, 7.6.x
-
Component/s: engine
-
None
Given a process with an intermediate throwing signal event that is specified for async and have a custom job retry configuration.
<intermediateThrowEvent id="failingSignalEvent"> <extensionElements> <camunda:failedJobRetryTimeCycle>R5/PT5M</camunda:failedJobRetryTimeCycle> </extensionElements> <signalEventDefinition signalRef="signal" camunda:async="true" /> </intermediateThrowEvent>
Problem:
When the signal is triggered and a failure occur during the transaction which follows the catch signal event then the custom retry configuration is not applied to the job and the default configuration is used.
- is related to
-
CAM-5116 Cannot use custom job retry cycle for non-service-task-like intermediate throwing events
-
- Closed
-