Hey @thibault ,

Glad to hear it is working again. I don't see any specific mention of a bug internally that would be related to this, but it is likely that it was due to a change in the underlying runtime for serverless compute.

This may be one of the tradeoffs you should consider with serverless vs. standard jobs compute. The lack of a need to manage the environment with serverless does help reduce the maintenance overhead, but could lead to inconsistent dependency issues with your code as you don't have as much control over the environment.