IgorChvyrov-sm

Hi @andyren0110, Thank you for reporting this issue! To help us investigate further, could you please share the version of the `conductor-python` library you're using? At the moment, I'm unable...

Hi @vyshnevskyi Thank you for reporting this issue! We've addressed it in PR #306. The fix will be included in our next release. Please feel free to test the changes...

Hi @arunksoman Thanks for reporting this issue! This appears to be the same pickling error that was discussed in [another thread](https://github.com/conductor-oss/python-sdk/issues/264). The solution has been provided there - please check...

Hi @anandthegreat Thanks for reporting this issue! To help us investigate, could you please share: 1. The version of the conductor-python library you're using 2. The version of Conductor you're...

Hi @anandthegreat I’m currently looking into this issue and will get back to you soon with an update. Thanks for your patience!

Hi @anandthegreat Thank you for your patience! Please try running Conductor using the Docker image from the README: `docker run --init -p 8080:8080 -p 5000:5000 conductoross/conductor-standalone:3.15.0` Let us know if...

@v1r3n Overall looks good, though could you tell why we continue using threads for async workers instead of one thread and event loop in it for handling all? From what...

> > @v1r3n Overall looks good, though could you tell why we continue using threads for async workers instead of one thread and event loop in it for handling all?...

Hey @shashanknr172-beep Thank you for reporting this issue. Maybe I'm missing something, but I cannot completely understand context of this issue. Could you please provide more details and context?

Hey @shashanknr172-beep Thanks for the clarification you provided. The think is that it isn't the proper repo to raise an issue in. The logic you provided is located in https://github.com/conductor-oss/conductor...