github-actions[bot] commented on issue #15832: URL: https://github.com/apache/dolphinscheduler/issues/15832#issuecomment-2050817393
### 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 there are parameters passed in the task node, the rerun function cannot be used. ### What you expected to happen Execute main task A. There is sub_process task B in the task flow of A. There is B1->B2 in the process of task B. The output parameters of B1 are passed to B2. The running type of main task A is "when starting the workflow". All tasks execute normally. If rerun is triggered, the task will fail to execute, and the failure node is the parameter passing node, as shown in the figure: <img width="988" alt="image" src="https://github.com/apache/dolphinscheduler/assets/30209856/7e4f7784-bc01-407a-93d0-304508f5e379";> ### How to reproduce Execute main task A. There is sub_process task B in the task flow of A. There is B1->B2 in the process of task B. The output parameters of B1 are passed to B2. The running type of main task A is "when starting the workflow". All tasks execute normally. If rerun is triggered, the task will fail to execute, and the failure node is the parameter passing node, as shown in the figure: <img width="988" alt="image" src="https://github.com/apache/dolphinscheduler/assets/30209856/7e4f7784-bc01-407a-93d0-304508f5e379";> ### Anything else _No response_ ### Version 3.2.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]
