ruanwenjun opened a new issue, #18596: URL: https://github.com/apache/dolphinscheduler/issues/18596
### Search before asking - [x] I had searched in the issues and found no similar issues. ### What happened The API currently validates the parameter format of sub-workflow tasks, but it does not consistently validate whether the referenced workflow is available in the current project context before persisting or activating the definition. As a result, an unavailable sub-workflow reference can be retained and handled inconsistently by later lifecycle operations. ### What you expected to happen Sub-workflow references should be validated consistently before task definitions are persisted or activated. Missing or unavailable references should be rejected with the same API result across workflow and task lifecycle operations. ### How to reproduce 1. Prepare a sub-workflow reference that is not available in the current project context. 2. Submit a workflow definition containing a sub-workflow task with that reference. 3. Observe that the definition can be saved without validating the referenced workflow consistently. ### Anything else The validation should cover workflow creation and updates, workflow-instance updates, version switching, and online or release operations. ### Version `dev` ### 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. -- 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]
