live-streaming-warning event; details.endpoints is the same on both.
Common causes:
- An endpoint update that the media server rejected: removing every destination (stop the live stream instead), adding an
hlsendpoint to a running stream, or a destination the media server does not recognize. - A single RTMP destination that stopped accepting media. The media server drops that destination and keeps streaming to the others.
- A stream started with a layout option the active compositor cannot honor.
Live stream updates are applied asynchronously. The REST API and daily-js only confirm that a request was accepted, and the
streaming.updated event only confirms it was processed. Watch this event to learn whether a change actually took effect; details.endpoints names the destinations concerned.Common fields
Represents the version of the event. Uses semantic versioning to inform a consumer if the payload has introduced any breaking changes.
An identifier representing this specific event. Treat it as opaque; its leading segment identifies the webhook configuration the event was delivered to.
Documenting when the webhook itself was sent. This timestamp is different than the time of the event the webhook describes.
Payload
Context for the warning.
endpoints(string[]): the destinations the warning is about: thestreaming_endpointsname when the destination was given by name, otherwise thescheme://host[:port]of the RTMP URL. The full URL carries the stream key and is never sent. Present only when known.