Hi Lucian
The problem with starting this kind of processing from inside Resilient is that it's usually a asynchronous task, and Resilient workflows were designed to work synchronously (except when it waits for a human task).
Even the python script workflow task is subject to very limited constraints, such as 5 seconds to complete, no more than X lines of code executed by the python interpreter (which runs as an outside process in the same server, the scripting-service) and a limited amount of entities created in the same workflow (500 I think). Not all libraries can be used, there's a library "whitelist", and so on.
The python code you run inside Resilient is subject to several restrictions. That's probably why it works in your desktop but not from inside Resilient.
Can you provide more details about what exactly you need to do and how you're trying to address the issue?
------------------------------
[]
Leonardo Kenji Shikida
------------------------------