I think you need to make this package somehow available. One option is to have it already preinstalled /cached on the target machine

Ok. Can I check that only the main script was stored in the task but not the dependent packages?

I guess the more correct way is to upload to some repo where the remote task can still pull from it?

Hi OddShrimp85 , have you run this task remotely? If you are importing your own package, how is it connected to the task?

Hi CostlyOstrich36 I have run this task locally at first. This attempt was successful.

When I use this task to run in a pipeline (task was run remotely), it cannot find the external package. This seems logical but I not sure how to resolve this.

Nope. In my local drive

is the external package is in some private repo?

Exactly 🙂