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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to