We have fixed an issue causing Control Room scheduler to incorrectly start multiple runs for a subset of scheduled runs between Oct 19 16:15 EEST (6.15am PT) and Oct 20 10:20 EEST (1.20am PT).
The root cause of the issue was an insufficient timeout configuration, which in some cases caused our resiliency mechanism to trigger a retry before the processing of the original request had been completed.