Orchestrator: advanced scenarios for healthcheck
Description
CAPL - Story default text according to the team DoR (Definition of Ready)
01 - STAKEHOLDER (PERSON THAT CAN VALIDATE AND ANSWER QUESTIONS):
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
Return unhealth if no task were created last 30 min.
04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:
- Return unhealth if no task were created last 30 min.
Activity
Show:
Details
Priority
HighestAssignee
Ingo Wagner
Reporter
Robson Thanael Poffo
Labels
CAROL_BACKLOG_REVIEWPLANNED
Due Date
4 March 2024
Fix versions
CAPL_4.00
Components
SQL_PIPELINES | ORCHESTRATOR
Created
26 January 2024, 17:17
Updated
12 March 2024, 21:18
More fields
Created: 26 January 2024, 21:17
Updated:
13 March 2024, 01:18
@Robson Thanael Poffo ,
@Gabriel DAmore Marciano , @Ingo Wagner , @Douglas Coimbra Lopes
This issue was planned to be delivered until 2024-03-04. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-02-12, 2024-03-04
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
@Jonathan Willian Moraes @Chámam Diomede Caires We will wait for the product team’s tests before closing this card.
@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-02-12. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-02-12
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.