Scheduling my stream delivery

While many contents need to be delivered on a 24/7 basis, other contents (for example, sport games) are typically only delivered during events that last a few hours or a few days.
Link allows to schedule the distribution of such content only for the duration of the events. This allows to save on cost, or to restrict content availability to the chosen time ranges.

Link Scheduler is available as part of the Premium Plan. Please contact us if you need to activate it for your organization.

The vocabulary

A pool contains inputs and outputs.
A link connects one input to one or more outputs. Content only flows on a path that is both linked and enabled.
An input is ingested when it is enabled. You can ingest continuously (24/7), or only during the event.
An output delivers to one receiver.
An output is either linked (attached to an input) or unlinked.

Creating a scheduled event

Within a pool, scheduled events can be used to manage the distribution of content from inputs to outputs from the pool.

Creating a scheduled event

A scheduled event applies to one or several inputs of a given pool. At defined times, link from event inputs to their outputs will be set to the required state : at start time, inputs and outputs are enabled, link are created, at end time, link are removed and inputs and outputs are disabled.

You can always manually enable or disable the link from an input to its output, for example to perform some tests, or to adapt to last-minute changes.

If at event start time, link is already enabled for an input, no change will be performed, as content is already streamed.

Disable or Enable SRT Links in a manual way

Connections and the scheduler

Scheduled events manage the delivery of content from inputs to outputs. Links between inputs and outputs are created at event start and released at event end.

On outputs, the connection should be pre-configured and tested with receivers before the event starts. To maximize flexibility, outputs are released at the end of each event, so they can be reused by another event with a different input. As a result, the output's IP address may change between events.

No content will be streamed during a scheduled event if connections are not properly established.

Choose your output SRT type

SRT Caller outputs: the source IP can change from one event to the next. If the receiver requires CIDR-based whitelisting, the whitelist must be updated at the start of each event. Otherwise, the receiver should be configured to accept connections without a fixed-IP requirement.
SRT Listener outputs are not recommended. Since the URL/IP changes between events, it cannot be reliably shared with receivers in advance.

For scheduled events, we therefore recommend SRT Caller outputs, with the receiver either accepting connections without fixed-IP filtering, or prepared to update its CIDR whitelist at each event start. See How to choose your inputs and outputs SRT type?.

What is kept and what is cleared

The scheduler only unlinks the links it created.
At event start, the scheduler links the inputs and outputs referenced in the event. At event end, it unlinks those same outputs. When an output is unlinked, its configuration is cleared. For an SRT Listener output, the part that goes away is the dynamic Link IP:Port.
These outputs are not unlinked at event end:

outputs you linked manually during the live event;
outputs that were already linked before the event started, because the scheduler did not link them.

Why the SRT details only appear once an output is linked

An unlinked output is a floating resource. Its connection details are assigned when it is linked, because the schedule decides which input it will serve. The IP:Port is not defined in advance: it exists only while the output is linked.

The messages you will see

When you create a schedule, under the end time field: the scheduler will disable and unlink the objects.
When you remove an object manually: the outputs will be unlinked and disabled.

Neither message says that the SRT Listener IP:Port will be cleared. Plan for it, and re-issue the connection details after the event wherever you used Listener outputs.

Managing a scheduled event

A scheduled event is either scheduled (start time is in the future), started (start time is in the past, end time is in the future), or finished (end time is in the past).

The temporal nature of scheduled events adds some restriction on modification possibilities. For example, the start time of a started event can't be modified, but its end time can be extended.

List of scheduled events

Adding an output while an event is running

You can manually link and enable an output that is not referenced in the event schedule while the event is running — for example a late receiver, or a fix during an incident.
That output is not torn down at event end. The scheduler only unlinks and disables the outputs it created. The input it is linked to also stays active, because the scheduler counts it as being in use.
So the input keeps ingesting and the output stays linked, and both keep being billed after the event ends. There is no automatic cleanup: you must disable and unlink what you added yourself.
We recommend creating a second scheduled event containing the new output instead.

Do not stop an event to make a change

Stopping or ending an event that is in progress triggers the end-time actions: the outputs are unlinked and disabled, and for Listener outputs the IP:Port is cleared. Only do it if you really want to interrupt every output.

You need to…	Do this
Run longer	Extend the end time of the started event. Do not stop and recreate it.
Make a controlled change	Enable or disable that specific link manually, instead of touching the whole event.
Recover from a source or network failure	Rely on the dual input you set up in advance — see Select your availability mode.

Updated on: 10/09/2026

Was this article helpful?

Thank you!