No spinner initialized

[solkrans]

Describe the bug
Running element run --export --mu after a stage is complete often after my second or third stage this exception happens:
Error: No spinner initialized with name e3d6a13a-b3af-475d-894b-0c632c604220
at Spinnies.setSpinnerProperties (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules\spinnies\index.js:107:37)
at Spinnies.update (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules\spinnies\index.js:55:10)
at onWorkerReport (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules@flood\element-scheduler\dist\src\Scheduler.js:199:39)
at Worker.onProcessReport (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules@flood\element-scheduler\dist\src\Worker.js:138:49)
at Worker. (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules@flood\element-scheduler\dist\src\Worker.js:39:30)
at Generator.next ()
at C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules@flood\element-scheduler\dist\src\Worker.js:8:71
at new Promise ()
at __awaiter (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules@flood\element-scheduler\dist\src\Worker.js:4:12)
at Worker.onMessage (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules@flood\element-scheduler\dist\src\Worker.js:27:40) Error: No spinner initialized with name e3d6a13a-b3af-475d-894b-0c632c604220
at Spinnies.setSpinnerProperties (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules\spinnies\index.js:107:37)
at Spinnies.update (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules\spinnies\index.js:55:10)
at onWorkerReport (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules@flood\element-scheduler\dist\src\Scheduler.js:199:39)
at Worker.onProcessReport (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules@flood\element-scheduler\dist\src\Worker.js:138:49)
at Worker. (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules@flood\element-scheduler\dist\src\Worker.js:39:30)
at Generator.next ()
at C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules@flood\element-scheduler\dist\src\Worker.js:8:71
at new Promise ()
at __awaiter (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules@flood\element-scheduler\dist\src\Worker.js:4:12)
at Worker.onMessage (C:\Users[username]\AppData\Roaming\npm\node_modules\element-cli\node_modules@flood\element-scheduler\dist\src\Worker.js:27:40)

To Reproduce
Steps to reproduce the behavior:
Really not sure. Here are my settings at least
export const settings: TestSettings = {
// userAgent: 'flood-chrome-test',
// loopCount: 1,

// Automatically wait for elements before trying to interact with them
waitUntil: 'visible',

actionDelay: '1s',
stepDelay: '2s',

stages: [
	{ duration: '1m', target: 3 },
	{ duration: '1m', target: 6 },
	{ duration: '1m', target: 12 },
	{ duration: '1m', target: 24 },
],

}

Expected behavior
I expect the run to finish.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Node.js version: 16.16.0
• Element Version: 2.0.4

Additional context
The website I'm testing has a lot of console output so the terminal is very busy during the run. I wish I could turn off console outputs and only have element print outs.