github-actions[bot] commented on issue #14625: URL: https://github.com/apache/dolphinscheduler/issues/14625#issuecomment-1646769841
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened In special cases, the conditions task cannot be triggered to execute. As shown in the following figure, when s7 finish before s1, task c2 cannot be triggered, resulting in task s5 or s6 cannot be triggered. The condition for task c2 is or. (When task s7 is completed before task s1 and the condition of c2 is defined as or, s4 is skipped and condition type task c2 cannot be triggered, resulting in the failure of subsequent s5 or s6 tasks to be executed. s1 to s6 are all sleep 20s, and s7 is sleep 10s) The workflow is shown below. Tasks s1 to s6 are shell tasks with sleep 20s. Task s7 is a shell type task and is sleep 10s.  Condition task c1 is defined as shown in the following figure:  Condition task c2 is defined as shown in the following figure:  ### What you expected to happen Condition type task c2 is defined as OR, then it should be executed as long as one of the preceding tasks is completed. (Condition type task c2 is defined as OR, it should be triggered as long as one of the predecessor tasks is completed.) ### How to reproduce Build the workflow shown above. As long as task s7 finishes before task s1, and the c2 task condition is or, the problem can be repeated (Construct the workflow as shown above, as long as task s7 is executed before task s1, and the task condition of c2 is or, the problem that c2 cannot be executed can be reproduced) ### Anything else _No response_ ### Version 3.1.x ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
