Bug description:
A service containing multiple conditional branches connected to different Next Service nodes returns the output of one Next Service branch instead of the branch that was executed.
- Create a service with multiple Conditional nodes.
- Connect each condition to a different Next Service node.
- Configure each Next Service node to open a different service.
- Save and trigger the service using an input that matches one of the earlier conditional branches.
The generated DSL uses one shared return block, but it references only one Next Service result variable. In the supplied DSL, return_next_service_res always returns ${järgmine_teenus_3_result.response ?? ''}, including after järgmine_teenus_1 or järgmine_teenus_2 has executed.
Expected behavior:
Each conditional branch must return the response from the Next Service node that was executed for that branch.
Services to test with:
arvutihiire_probleem_2026_09_10_14_53_37.json
ekraani_probleem_2026_09_10_14_53_37.json
klaviatuuri_probleem_2026_09_10_14_53_37.json
seadme_probleem_2026_09_10_14_53_37.json
Bug description:
A service containing multiple conditional branches connected to different Next Service nodes returns the output of one Next Service branch instead of the branch that was executed.
The generated DSL uses one shared return block, but it references only one Next Service result variable. In the supplied DSL,
return_next_service_resalways returns${järgmine_teenus_3_result.response ?? ''}, including afterjärgmine_teenus_1orjärgmine_teenus_2has executed.Expected behavior:
Each conditional branch must return the response from the Next Service node that was executed for that branch.
Services to test with:
arvutihiire_probleem_2026_09_10_14_53_37.json
ekraani_probleem_2026_09_10_14_53_37.json
klaviatuuri_probleem_2026_09_10_14_53_37.json
seadme_probleem_2026_09_10_14_53_37.json