Does having two dependencies with the same name can cause issue?

Hey @Maximilien_Selva To avoid complications and versioning issues, it’s recommended to use the same version of dependencies across both orchestrators (tenant and host). If that’s not feasible, ensure your automation packages are self-contained and specify the required versions within the package. This way, you reduce the risk of dependency conflicts and improve the stability of your workflows.

cheers