Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why does pyzeebe always "return" all task variables on job completion? #321

Open
datakurre opened this issue Aug 17, 2022 · 0 comments
Open

Comments

@datakurre
Copy link

datakurre commented Aug 17, 2022

I am curious about this decision:

job.variables.update(original_return_value)

Why does pyzeebe always return all fetched task variables on job completion instead of just returning the variables returned by the worker?

Run into this when parallel multi-instance task was not behaving as expected, because pyzeebe ended up overwriting output collection variable (once it had been set after first completed worker). As a result, my multi-instance task's output collection was mostly filled with null values.

After patching variables dictionary to clean up variables on update on after_job hook my parallel multi-instance task was fixed to return expected output collection.

@datakurre datakurre changed the title Why does pyzeebe always "return"all task variables on job completion? Why does pyzeebe always "return" all task variables on job completion? Aug 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant