github-actions[bot] commented on issue #18014: URL: https://github.com/apache/dolphinscheduler/issues/18014#issuecomment-3995662596
### 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 I interrupted a running task in DolphinScheduler. The workflow instance status changed to "Ready to Stop" but got stuck in this state indefinitely. Because of this stuck instance, I cannot delete the corresponding workflow definition. When I try to delete it, the system throws the following error: `Failed to delete workflow definition, there are [4] running workflow instances using it`. (I have attached the screenshots of the stuck status and the error message below.) <img width="2094" height="144" alt="Image" src="https://github.com/user-attachments/assets/89a6f61a-1dba-4b9a-887c-ecd3f9ecf220"; /> ### What you expected to happen 1. After clicking the "Stop" button, the workflow instance should transition to the "Stopped" state normally and promptly. 2. The instance should not get stuck in the "Ready to Stop" status indefinitely, which currently blocks the deletion of the workflow definition. <img width="2160" height="131" alt="Image" src="https://github.com/user-attachments/assets/4960a1de-d997-46bd-a1c2-140a8e239903"; /> ### How to reproduce 1. Create a workflow with a Shell task. 2. In the Shell task, write: `echo "param from p-a:${var1}"`. 3. Configure a custom parameter for this task: - Prop: `var1` - Direct: `IN` - Type: `VARCHAR` - Value: `${var1}` (pointing to a global or outer parameter). 4. Start the workflow instance without providing any input value for `var1` (leaving the parameter unassigned/unresolved). 5. While the workflow is in the "Running" or "Dispatching" state, manually click the "Stop" button in the Workflow Instance list. 6. **Observation**: The workflow instance status transitions to "Ready to Stop" (准备停止) but hangs there indefinitely. It never reaches the "Stopped" state, even after a long wait. 7. **Consequence**: This "Ready to Stop" state blocks the deletion of the workflow definition, reporting that "1 running instances are using it". ### Anything else _No response_ ### Version 3.4.0 ### 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]
