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
found a bug with task type SWITCH. If the defaultCase contains some task but the other cases do not, the execution will go through the defaultCase even if the SWITCH task correctly evaluated to one of the other branches.
This workflow always goes through the defaultCase branch, thus resulting in a workflows status of FAILED, even though it should go through the "true" case and thus skip the termination task and go to the end of workflow having status of COMPLETED.
Please see that even the diagram is wrong:
The evaluation is correctly true, but the termination task is ticked and the arrow is green both on the true branch and going from the termination task towards the end of workflow.
Interestingly, if I place at least one task inside the true branch, the workflow will correctly execute through that branch.
If this is intended behaviour, it is not documented. I consider it a bug.
I have also tried with the value-param evaluator, but the behavior was the same.
Hello all,
found a bug with task type SWITCH. If the defaultCase contains some task but the other cases do not, the execution will go through the defaultCase even if the SWITCH task correctly evaluated to one of the other branches.
A simple workflow to reproduce:
Takes no inputs, just run it from workbench.
This workflow always goes through the
defaultCase
branch, thus resulting in a workflows status of FAILED, even though it should go through the "true" case and thus skip the termination task and go to the end of workflow having status of COMPLETED.Please see that even the diagram is wrong:
The evaluation is correctly
true
, but the termination task is ticked and the arrow is green both on thetrue
branch and going from the termination task towards the end of workflow.Interestingly, if I place at least one task inside the
true
branch, the workflow will correctly execute through that branch.If this is intended behaviour, it is not documented. I consider it a bug.
I have also tried with the
value-param
evaluator, but the behavior was the same.Details
Conductor version: 3.21.11 + 69 commits
Persistence implementation: Postgres
Queue implementation: Redis
Lock: Redis
Expected behavior
The workflow should go through the
true
branch.The text was updated successfully, but these errors were encountered: