This is an issue when you have two jobs running concurrently and both use BrowserstackLocal. Both start with the "localIdentifier" option, but when stopping it doesn't use the "localIdentifier". This makes it so that when the first job finishes executing, it will stop ALL BrowserstackLocal processes using the same Browserstack key, therefore crashing the second job's execution.