github-actions[bot] commented on issue #17214: URL: https://github.com/apache/dolphinscheduler/issues/17214#issuecomment-2911013614
### 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 Version: 3.2.2. Phenomenon: There is a workflow A, there is a task a, there is a workflow B, there is a task b, b depends on a, depends on the current hour, and the waiting dependency is configured to complete, the timeout time is 1 minute. The strategy is timeout alarm + timeout failure. When workflow B is scheduled, task a runs for more than 1 minute or does not run. The dependency node a in workflow B neither alarm nor failure after more than 1 minute. It is in a state of running all the time. If workflow B does not stop workflow B manually, it will continue to run. ### What you expected to happen When workflow B is scheduled, if the dependent node a exceeds the configured timeout time, its status is not successful, an alarm should be issued and marked as failed, rather than waiting all the time, causing workflow B to wait forever ### How to reproduce No special configuration, 3.2.1 3.2.2 can be reproduced ### Anything else It will definitely happen ### Version 3.2.x ### Are you willing to submit PR? - [ ] 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]
