njnu-seafish opened a new issue, #17771: URL: https://github.com/apache/dolphinscheduler/issues/17771
### 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 importing tasks such as ConditionTask and SwitchTask, the TaskCode references within the task parameters are not being replaced correctly. such as: > { "localParams" : [ ], "varPool" : [ ], "dependence" : { "dependTaskList" : [ { "dependItemList" : [ { "dependentType" : null, "projectCode" : 0, "definitionCode" : 0, "depTaskCode" : 157103251016960, "cycle" : null, "dateValue" : null, "dependResult" : null, "parameterPassing" : false, "status" : "SUCCESS" } ], "relation" : "OR" } ], "relation" : "AND" }, "conditionResult" : { "conditionSuccess" : false, "successNode" : [ 157101634027776 ], "failedNode" : [ 157101657370880 ] } } Fields such as depTaskCode, successNode, and failedNode still reference the task codes of the old tasks. ### What you expected to happen Fields such as depTaskCode, successNode, and failedNode still reference the task codes of the new tasks. ### How to reproduce 1. Create a workflow containing tasks such as ConditionTask, SwitchTask, etc., and then export the workflow. 2. Then, when importing the above workflow, you will find that the task codes referenced in the parameters of the new workflow's tasks are incorrect. ### Anything else _No response_ ### 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](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]
