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
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.
The text was updated successfully, but these errors were encountered:
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
I am curious about this decision:
pyzeebe/pyzeebe/task/task_builder.py
Line 36 in 0586dfe
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.
The text was updated successfully, but these errors were encountered: