I think you are right.
BTW, would you also consider the following two scenarios?? 1. The relied node has a retry attribute. 2. The dependent node needs all task instances of relied node to be successful in dependent cycle. For example: - node A run hourly - node B run daily. And when all tasks of node A are executed successfully, node B executes For second scenario, add some tags to successfully executed task may be a possible solution. ------------------ ???????? ------------------ ??????: "wenhemin"<[email protected]>; ????????: 2020??5??12??(??????) ????5:26 ??????: "dev"<[email protected]>; ????: [DISCUSS] Dependent task check rules Hello! Abort dependent task check rules, I think the current implementation is problematic. E.g. check logic: this week The current implementation: 1.get this Monday 2.the date list of this Monday to current date??asc order?? 3.Iterate through the list of dates in sequence to check the status of all process instances. There is a failure, the ultimate is failure state. I think, the check logic should be: 1.get date range, start date and end date 2.if type is DEPENDENT_ALL query the first process instance in reverse order, check this instance state. 3.if type is non DEPENDENT_ALL query the first task instance in reverse order, check this instance state.
