1205747671 opened a new issue, #14618: URL: https://github.com/apache/dolphinscheduler/issues/14618
### 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 am using the API projects/{projectCode}/executors/start-process-instance to run multiple instances of the same serial waiting workflow in a rapid manner, such as in a for loop. Theoretically, these instances should execute in order. However, I've observed that some instances are executing concurrently, not following the expected waiting order. ### What you expected to happen I have previously reported this issue but it doesn't appear to have been resolved yet. ### How to reproduce Using a for loop to call the interface to start the same workflow 10 times may result in multiple direct runs. ### Anything else I suspect the issue might be related to transactions. I temporarily resolved this by appending 'for update' at the end of 'queryByProcessDefineCodeAndProcessDefinitionVersionAndStatusAndNextId' SQL. Is there a better solution? ### 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]
