You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "tookbra (via GitHub)" <gi...@apache.org> on 2026/04/02 18:26:59 UTC
[I] [Bug] [Module Name] Workflow instance stuck in RUNNING state forever when using CONTINUE failure strategy with a failed upstream task [dolphinscheduler]
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: commits-unsubscribe@dolphinscheduler.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] Workflow instance stuck in RUNNING state forever when using CONTINUE failure strategy with a failed upstream task [dolphinscheduler]
Posted by "tookbra (via GitHub)" <gi...@apache.org>.
tookbra commented on issue #18131:
URL: https://github.com/apache/dolphinscheduler/issues/18131#issuecomment-4182224196
>  
>
> The final state of workflow is a failure, so I can't reproduce your issue.
>
> However, the `CONTINUE` failure strategy really didn't take effect.
The last task to complete in the workflow happens to be a SUCCESS task that has downstream nodes, but those downstream nodes cannot be triggered because other predecessor tasks have already failed.
工作流中最后一个完成的任务恰好是 SUCCESS，且它有下游节点，但该下游节点因其他前驱失败而无法被触发
你可以尝试success_task_1节点等待几秒保证最后一个成功
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] [Module Name] Workflow instance stuck in RUNNING state forever when using CONTINUE failure strategy with a failed upstream task [dolphinscheduler]
Posted by "SbloodyS (via GitHub)" <gi...@apache.org>.
SbloodyS commented on issue #18131:
URL: https://github.com/apache/dolphinscheduler/issues/18131#issuecomment-4181335659
The final state of workflow is a failure, so I can't reproduce your issue.
However, the `CONTINUE` failure strategy really didn't take effect.
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] Workflow instance stuck in RUNNING state forever when using CONTINUE failure strategy with a failed upstream task [dolphinscheduler]
Posted by "SbloodyS (via GitHub)" <gi...@apache.org>.
SbloodyS commented on issue #18131:
URL: https://github.com/apache/dolphinscheduler/issues/18131#issuecomment-4204613523
Thank you for your feedback. I've successfully reproduce this issue. I've created PR to fix this. It will be released in version 3.4.2. @tookbra
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] [Module Name] Workflow instance stuck in RUNNING state forever when using CONTINUE failure strategy with a failed upstream task [dolphinscheduler]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #18131:
URL: https://github.com/apache/dolphinscheduler/issues/18131#issuecomment-4179672892
### 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.
When the workflow is configured with the **CONTINUE** failure policy and some upstream tasks fail to execute,
Downstream nodes that depend on both successful and failed tasks will never be triggered.
At this point `activeTaskExecutionRunnable` is empty, but `emitWorkflowFinishedEventIfApplicable()`
It never gets called, causing the workflow instance to stay in the RUNNING state forever and cannot be ended.
### 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.
When all tasks have been executed (whether successful or failed), even if some downstream tasks failed to trigger due to upstream failure,
The workflow should also transition to the FAILURE state normally instead of being stuck running forever.
### 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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] Workflow instance stuck in RUNNING state forever when using CONTINUE failure strategy with a failed upstream task [dolphinscheduler]
Posted by "SbloodyS (via GitHub)" <gi...@apache.org>.
SbloodyS closed issue #18131: [Bug] Workflow instance stuck in RUNNING state forever when using CONTINUE failure strategy with a failed upstream task
URL: https://github.com/apache/dolphinscheduler/issues/18131
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org