| 1 |
--- |
| 2 |
fixes: |
| 3 |
- | |
| 4 |
Workflow execution integrity checker mechanism was too aggressive in case |
| 5 |
of big workflows that have many task executions in RUNNING state at the |
| 6 |
same time. The mechanism was selecting them all in one query and calling |
| 7 |
"on_action_complete" for each of them within a single DB transaction. |
| 8 |
That could lead to situations when this mechanism would totally block |
| 9 |
all normal workflow processing whereas it should only be a "last chance" |
| 10 |
aid in case of real infrastructure failures (e.g. MQ outage). |
| 11 |
This issue has been fixed by adding a configurable batch size, so that |
| 12 |
the checker can't select more than this number of task executions in |
| 13 |
RUNNING state at once. |