tookbra opened a new issue, #18131: URL: https://github.com/apache/dolphinscheduler/issues/18131
### 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 When a workflow uses the **CONTINUE** failure strategy and some upstream tasks fail, the downstream task that depends on **both successful and failed predecessors** can never be triggered. As a result, `activeTaskExecutionRunnable` becomes empty but `emitWorkflowFinishedEventIfApplicable()` is never called, leaving the workflow instance stuck in `RUNNING` state indefinitely. 当工作流配置了**继续（CONTINUE）**失败策略，且部分上游任务执行失败时， 同时依赖成功任务和失败任务的下游节点将永远无法被触发。 此时 `activeTaskExecutionRunnable` 已为空，但 `emitWorkflowFinishedEventIfApplicable()` 始终得不到调用，导致工作流实例永远停留在**运行中（RUNNING）**状态，无法结束 ### What you expected to happen The workflow should eventually transition to `FAILURE` state once all tasks have finished (either successfully or with failure), even if some downstream tasks could not be triggered due to failed predecessors. 当所有任务都已执行完毕（无论成功还是失败），即使部分下游任务因上游失败而未能触发， 工作流也应正常转换为**失败（FAILURE）**状态，而不是永远卡在运行中。 ### How to reproduce <img width="1142" height="100" alt="Image" src="https://github.com/user-attachments/assets/3762d433-d1fe-4411-ad40-946b31fac941"; /> <img width="1197" height="612" alt="Image" src="https://github.com/user-attachments/assets/1647e833-5321-4430-b129-f6c553951388"; /> ### Anything else _No response_ ### Version 3.4.1 ### 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]
