flowable / flowable/flowable-engine

multiInstance subprocess of revoking tasks has bug

Open
#3,999 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
9.5k
Forks
2.9k
Avg merge
7h 8m
Merged PRs (30d)
2

Description

**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](https://github.com/user-attachments/assets/0cdcb964-9612-4390-805b-c95bebc4b5fd)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the multi-instance subprocess sequence shown in the issue on Flowable 6.8.1, using taskService.complete(taskBo.getTaskId(), processVariables). Trace the failure around the reported missing outgoing sequence flow from Activity_1xk5x7b. Done means the A/B revoke sequence completes correctly and a regression test covers it.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.