-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] [Master] The subprocess type node is always in the ready stop state(3.1.x) #14169
Comments
Search before asking
What happenedThe failure strategy of the parent process instance is end, and the parallelism strategy is selected. When there are many subprocess type nodes, some subprocess instances have run successfully, but the subprocess task instances in the parent process have not been updated to complete status. At this time, a subprocess type node fails, and the parent process will kill all surviving tasks. Instance, all surviving subprocess-associated subprocess instances will be forcibly updated to the ready stop state, resulting in task instances in the parent process not being able to be updated, so it always shows that the submission is successful, or the running state
What you expected to happenbe right How to reproducebe right Anything elseNo response Version3.1.x Are you willing to submit PR?
Code of Conduct
|
Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
|
…pause ``` or ``` ready stop ``` state
…``` or ``` ready stop ``` state (#14170)
Search before asking
What happened
父流程实例的失败策略为结束,并且选择并行策略。当subprocess类型节点很多的时候,一部分子流程实例已经运行成功,但是subprocess 在父流程中的任务实例还未更新成完成状态,此时一个subprocess 类型节点失败了,父流程会杀死所有存活的任务实例,所有存活的subprocess关联的子流程实例会被强制更新为ready stop 状态,导致父流程中的任务实例无法更新,所以一直显示提交成功,或者运行中状态
What you expected to happen
be right
How to reproduce
be right
Anything else
No response
Version
3.1.x
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: