AItale-4 opened a new issue, #17572: URL: https://github.com/apache/dolphinscheduler/issues/17572
### 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 the workflow execution type is Serial Priority, quickly triggering the same workflow multiple times (e.g., three times) will generate multiple workflow instances. Among them: - The first two workflow instances remain stuck in the READY_STOP state; - Their corresponding task instances remain in RUNNING_EXECUTION state（the task type is DEPENDENT）; - It is impossible to stop them either via UI or API. When attempting to stop a task instance using the API: `POST /dolphinscheduler/projects/{projectCode}/task-instances/{id}/stop` The API returns failure, and the following error appears in the master log: ``` org.apache.dolphinscheduler.remote.handler.NettyServerHandler:[140] - [WorkflowInstance-0][TaskInstance-0] - commandType TASK_KILL_REQUEST not support ``` ### What you expected to happen - Workflow and task instances should correctly transition to the “STOPPED” state when manually stopped (via UI or API), even under Serial Priority execution mode. ### How to reproduce 1. Create a workflow with execution type = Serial Priority. 2. Quickly trigger this workflow multiple times (e.g., 3 instances). 3. Workflow instances remain in READY_STOP state indefinitely. 4. The tasks inside these instances are of type DEPENDENT, and remain in RUNNING_EXECUTION state (they keep running and cannot be stopped). 5. Try to stop these tasks via the UI or /task-instances/{id}/stop API. 6. Check dolphinscheduler-master.log, error appears as shown above. ### 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]
