Only one livestream is ever actually being streamed to at a time. The very first scheduled
livestream gets the main key. Every livestream scheduled after that gets the same temporary
key — they are queued, not concurrent — and each one is promoted to the main key in turn (see
shouldPromoteTempToMain) once the livestream ahead of it has ended and its own start time
is approaching. There is intentionally no cap on how many livestreams can be scheduled
this way.
Only one livestream is ever actually being streamed to at a time. The very first scheduled livestream gets the main key. Every livestream scheduled after that gets the same temporary key — they are queued, not concurrent — and each one is promoted to the main key in turn (see
shouldPromoteTempToMain) once the livestream ahead of it has ended and its own start time is approaching. There is intentionally no cap on how many livestreams can be scheduled this way.