You need to sign in or sign up before continuing.
There was an error opening the run if its JSON cache file didn't already exist, because it tried to use multiprocessing inside multiprocessing, which is not allowed. This avoids that scenario. Behaviour should be unchanged if the cache file exists.
No specific tests, but the parallelize=False option was added for precisely this use case - where you're already using a multiprocessing pool outside opening the run - so I'm confident in it.