Competing Package Activity Dependencies

We have four separate robot machines connected to orchestrator, each with their own local activities folder containing all of the activities that were needed at any time for that machine. When we publish a workflow to orchestrator and try to run it on other machines in the same environment we get error messages:

Could not load file or assembly ‘CsvHelper, Version=, Culture=neutral, PublicKeyToken=8c4959082be5c823’ or one of its dependencies. The system cannot find the file specified.

There are often multiple file or assembly errors, and we have to manually resolve each one by uninstalling the package from that machine or by copying a package from one machine to another.

It was my understanding (per About the Activities Feed) that the necessary activities should be pulled straight from Orchestrator Nuget Activities whenever needed, so there shouldn’t be package dependency issues when running a robot. How can we resolve these errors without manually handling each individual package?