starrysxy commented on issue #16285: URL: https://github.com/apache/dolphinscheduler/issues/16285#issuecomment-2219783629
> I think I know what your problem is. The current dependency node check will get the latest workflow instance to verify that the task instance in it meets the configuration conditions. However, this judgment does not take into account the case of manually starting individual tasks, which can only execute some of the nodes. This scenario calls for a solution discussion. > > cc @caishunfeng @ruanwenjun @EricGao888 @rickchengx Yes, that's what I mean. Btw, my version is 3.1.8.(The logic of this part is still the same in later versions). I have checked the code, and I think this scenario is common, especially if you've just switched to DS from another dispatch system. Because tasks will not be migrated all at once, but will be migrated one by one, which means the process definition will be modified frequently. **Maybe we can start with these two places in the code:** 1. `org.apache.dolphinscheduler.server.master.utils.DependentExecute#calculateResultForTasks`  2. `org.apache.dolphinscheduler.server.master.utils.DependentExecute#getDependTaskResult`  -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
