-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
User Story (Required on creation):
As an operations engineer, I want to be able to define for the clean-up job a dedicated retry configuration. In the current Camunda version e.g. 7.16 the clean-up job uses the same retry configuration as all other jobs. In a shared-engine setup with e.g., asynchronous service tasks no retries for tasks is a possible setting (defaultNumberOfRetries=1). In this setup, I still want to benefit from clean-up retries to reduce manual interventions for short-term, temporary disruptions (Network, DB-timeouts).
Functional Requirements (Required before implementation):
Technical Requirements (Required before implementation):
Limitations of Scope (Optional):
Hints (optional):
This is the controller panel for Smart Panels app
[CAM-14694] Dedicated retry configurations for cleanup jobs
| Link | New: This issue is related to SUPPORT-13684 [ SUPPORT-13684 ] |
| Description |
Original:
h3. User Story (Required on creation):
h3. Functional Requirements (Required before implementation): h3. Technical Requirements (Required before implementation): h3. Limitations of Scope (Optional): h3. Hints (optional): |
New:
h3. User Story (Required on creation):
As an operations engineer, I want to be able to define for the clean-up job a dedicated retry configuration. In the current Camunda version e.g. 7.16 the clean-up job uses the same retry configuration as all other jobs. In a shared-engine setting with e.g., asynchronous service tasks no retries for tasks is a possible setting (defaultNumberOfRetries=1). Clean-up retry can avoid manual intervention for short-term, temporary disruptions (Network, DB-timeouts). h3. Functional Requirements (Required before implementation): h3. Technical Requirements (Required before implementation): h3. Limitations of Scope (Optional): h3. Hints (optional): |
| Summary | Original: Separate retry configuration for cleanup jobs | New: Dedicated retry configurations for cleanup jobs |
| Description |
Original:
h3. User Story (Required on creation):
As an operations engineer, I want to be able to define for the clean-up job a dedicated retry configuration. In the current Camunda version e.g. 7.16 the clean-up job uses the same retry configuration as all other jobs. In a shared-engine setting with e.g., asynchronous service tasks no retries for tasks is a possible setting (defaultNumberOfRetries=1). Clean-up retry can avoid manual intervention for short-term, temporary disruptions (Network, DB-timeouts). h3. Functional Requirements (Required before implementation): h3. Technical Requirements (Required before implementation): h3. Limitations of Scope (Optional): h3. Hints (optional): |
New:
h3. User Story (Required on creation):
As an operations engineer, I want to be able to define for the clean-up job a dedicated retry configuration. In the current Camunda version e.g. 7.16 the clean-up job uses the same retry configuration as all other jobs. In a shared-engine setup with e.g., asynchronous service tasks no retries for tasks is a possible setting (defaultNumberOfRetries=1). In this setup, I still want to benefit from clean-up retries to reduce manual interventions for short-term, temporary disruptions (Network, DB-timeouts). h3. Functional Requirements (Required before implementation): h3. Technical Requirements (Required before implementation): h3. Limitations of Scope (Optional): h3. Hints (optional): |
| Sprint | New: SOON - Customer commitment [ 95 ] |
| Rank | New: Ranked higher |
| Labels | Original: PM clean-up | New: PM clean-up history-cleanup |
| Sprint | Original: SOON - Customer commitment [ 95 ] | New: Potential for 7.19 [ 94 ] |
| Rank | New: Ranked higher |