Thomas-HuWei opened a new issue, #15849: URL: https://github.com/apache/dolphinscheduler/issues/15849
### 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 In newest version 3.2.1, force success has invalid. When master run one step of instance failed, I set the step to force success, but next time, this step run again and it's old record already been set to failure status.  I've search the code, find in file https://github.com/apache/dolphinscheduler/blob/3.2.1-release/dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java  In this position, you will update taskInstance in DB using your memory old data, that means when I use api to force success, the db record is changed, but next time here you override db state by your memory old state. And then I fix the record status, but the function force success is can't still work. There must be other bugs. ### What you expected to happen Force success can work successfully! ### How to reproduce Easy to produce, use the 3.2.1 version to deploy, and test force success function, it will must fail. ### Anything else _No response_ ### Version 3.1.x ### 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]
