Skip to content
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

multiInstance subprocess of revoking tasks has bug #3999

Open
luoyi1029 opened this issue Dec 11, 2024 · 6 comments
Open

multiInstance subprocess of revoking tasks has bug #3999

luoyi1029 opened this issue Dec 11, 2024 · 6 comments

Comments

@luoyi1029
Copy link

Describe the bug
In the multiInstance subprocess of departments,
if Receiver sends A and then withdraws, Receiver sends B and then withdraws, Receiver sends A and A sends B。
error : No outging sequence flow of element 'Activity_1xk5x7b' could be selected for continuing the process, How to solve it?

Code
taskService.complete(taskBo.getTaskId(), processVariables);

Additional context
Flowable 6.8.1
subProcess

@luoyi1029
Copy link
Author

16:57:22.349 [http-nio-9001-exec-2] ERROR c.g.c.c.GlobalExceptionAdvice - [validatedFlowableException,111] - 运行时异常:
org.flowable.common.engine.api.FlowableException: No outgoing sequence flow of element 'Activity_1xk5x7b' could be selected for continuing the process
at org.flowable.engine.impl.agenda.TakeOutgoingSequenceFlowsOperation.leaveFlowNode(TakeOutgoingSequenceFlowsOperation.java:251)
at org.flowable.engine.impl.agenda.TakeOutgoingSequenceFlowsOperation.handleFlowNode(TakeOutgoingSequenceFlowsOperation.java:155)
at org.flowable.engine.impl.agenda.TakeOutgoingSequenceFlowsOperation.run(TakeOutgoingSequenceFlowsOperation.java:105)
at org.flowable.common.engine.impl.AbstractEngineConfiguration.lambda$new$0(AbstractEngineConfiguration.java:138)
at org.flowable.engine.impl.interceptor.CommandInvoker.executeOperation(CommandInvoker.java:130)
at org.flowable.engine.impl.interceptor.CommandInvoker.executeOperations(CommandInvoker.java:114)
at org.flowable.engine.impl.interceptor.CommandInvoker.execute(CommandInvoker.java:72)
at org.flowable.engine.impl.interceptor.BpmnOverrideContextInterceptor.execute(BpmnOverrideContextInterceptor.java:26)
at org.flowable.common.engine.impl.interceptor.TransactionContextInterceptor.execute(TransactionContextInterceptor.java:53)
at org.flowable.common.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:105)
at org.flowable.common.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:52)
at org.flowable.common.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:30)
at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:56)
at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:51)
at org.flowable.engine.impl.TaskServiceImpl.complete(TaskServiceImpl.java:223)

@luoyi1029
Copy link
Author

process_send_doc-formkey.xml.txt
xml file

@filiphr
Copy link
Contributor

filiphr commented Dec 11, 2024

No outgoing sequence flow of element 'Activity_1xk5x7b' could be selected for continuing the process

Based on that error it means that there is no sequence flow that can be taken out of the user task with id 'Activity_1xk5x7b'. I can see that there is one sequence flow out of it. This sequence flow has a condition on it ${flag==11}, so I assume that the flag variable does not have the value of 11 and thus it is not possible to take that flow and there is no other flow that it can go out through.

Can you provide a reproducible example for this?

@luoyi1029
Copy link
Author

luoyi1029 commented Dec 11, 2024 via email

@luoyi1029
Copy link
Author

to Leader B complete()
variables = {flag=13, assigneeList=[155], deptId=100, assignee=156, bgsId=125, gateFlag=101}

@filiphr
Copy link
Contributor

filiphr commented Dec 12, 2024

@luoyi1029 can you provide a unit test showing this problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants