Skip to content
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.

variables are not getting set if the SET_VARIABLE task is followed by a workflow task #3771

Open
missioncoding opened this issue Sep 13, 2023 · 3 comments
Labels
type: bug bugs/ bug fixes

Comments

@missioncoding
Copy link

The conductor is not setting any variables when a SET_VARIABLE task is followed by a workflow.
This is easy to reproduce with a small workflow having a set variable followed by another workflow.

image

As shown in the attached workflow sample snippet. the set_output_variables_ref_1 is trying to set two variables user and param.
even after the successful execution of the task the varaibles are not set and they dont even appear in the varaibles pane under"Workflow Input/output"

Hence when the last task divide in the snippet tries to access the variable param it gets null

image

@missioncoding missioncoding added the type: bug bugs/ bug fixes label Sep 13, 2023
@missioncoding
Copy link
Author

I observe the same condition is true when the set variable task is followed by a switch task as well. the variables are not getting set globally. After the set variable task you can access using workflow.variables for the first access but post that the variable is getting set to null.

@v1r3n
Copy link
Contributor

v1r3n commented Sep 16, 2023

@missioncoding I believe this is a bug. Will send a PR to fix.

@missioncoding
Copy link
Author

Thanks @v1r3n. it would be great to get a fix asap.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug bugs/ bug fixes
Projects
None yet
Development

No branches or pull requests

2 participants