You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
Describe the bug
Running v3.13.8 with postgres indexing as show in the attached properties I start getting a task duplication error as show in the screenshot. The workflow termiates in error but in a completely non predictable way. Few task succed, few terminate with strange error condition, other are canceled.
dcore94
changed the title
Dynamic fork join with subworkflow does not work properly in v3.8.13 with postgres indexing
Dynamic fork join with subworkflow does not work properly in v3.13.8 with postgres indexing
Nov 13, 2023
I'm really getting in trouble with this issue. Can anyone please give some feedback? Can anyone at least tell if the relation to Netflix/conductor#3836 is correct?
Sorry for pressing but I'm really unable to understand how a project like Conductor can keep one such dangerous issue without any feedback for more than one month :-(
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Running v3.13.8 with postgres indexing as show in the attached properties I start getting a task duplication error as show in the screenshot. The workflow termiates in error but in a completely non predictable way. Few task succed, few terminate with strange error condition, other are canceled.
Details
Conductor version: 3.13.8 (community edition)
Persistence implementation: Postgres
Queue implementation: Postgres
Workflow definition: As attached in workflows.zip
Task definition:
Event handler definition:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should call 30 times the subworkflow and terminate correctly.
Screenshots
workflows.zip
Additional context
The property file
The text was updated successfully, but these errors were encountered: