The Broker Service must never be stopped or restarted while it is managing active recordings.
If the service is restarted during an ongoing recording, it will be unable to reconnect to the recording session already in progress. As a result, it will not be able to:
Monitor the recording status.
Apply any modifications requested after the recording has started.
Update the related asset information.
Properly associate the completed recording with the originating asset.
If the Broker Service becomes unavailable due to network issues, server failures, or workstation problems, there are only two ways to avoid losing the ongoing recording.
The safest approach is to allow the recording to continue until its scheduled end time.
In this scenario:
However, because the Broker Service lost control of the recording, the operator must perform a manual verification to ensure that the generated file has been correctly associated with the expected asset.
If the file has not been linked automatically, the operator must manually associate it with the appropriate asset following the standard operational procedure and, if required, manually start the After Ingest workflow.
Example
A recording is scheduled on asset XXX starting at 10:00 AM with a duration of 2 hours.
At 10:30 AM, the server hosting the Broker Service unexpectedly shuts down due to an external issue.
When the Broker Service is restarted, it cannot regain control of the recording that is already in progress.
The operator must wait until the scheduled end time (12:00 PM). The recording service will automatically stop the recording and finalize the media file. If the recording completes normally, the generated file is expected to be properly closed and linked to asset XXX. Nevertheless, the operator must verify that the association has been completed successfully.
If the asset association is missing, the operator must manually link the file from Media Library using the standard operational procedure and, if necessary, manually trigger the After Ingest workflow.
If the operator needs to stop a recording before its originally scheduled end time, this can still be done provided that the Broker Service has been restored and is running.
The operator must:
Example
An asset XXX starts recording at 10:00 AM with a scheduled duration of 2 hours.
At 10:30 AM, the Broker Service unexpectedly crashes. Once the Broker Service has been restored and is running again, the operator decides to stop the recording before its originally planned end time.
Since 30 minutes of recording have already elapsed, the operator must open the active recording from the Web interface and modify its duration to a value lower than the elapsed time, for example 20 minutes.
After the change is saved, the Broker Service detects that the configured duration has already been exceeded and automatically sends a stop command to the recording service. The recording is typically stopped within approximately 20 seconds of the modification.
Important
The Broker Service must be running. This procedure cannot be performed while the Broker Service is unavailable.
Once the recording has been stopped, the media file will be properly finalized, closed, and linked to the originating asset. Nevertheless, the operator must verify that the asset association has been completed successfully.
If the file has not been linked correctly, the operator must manually associate it with the appropriate asset following the standard operational procedure.
If the MultiIngest Client closes unexpectedly (for example, due to an application crash or a workstation failure) while one or more manual recordings are in progress, restarting the application will automatically reconnect it to the active recording sessions managed by the Ingest Service.
Once the reconnection has been completed, the operator can continue managing the recordings as if the interruption had never occurred.
The recorded media will not be lost. At the end of the recording, the media file will be properly finalized, closed, and linked to the corresponding asset.
However, because the MultiIngest Client was unexpectedly interrupted during the recording, the system will display a warning message advising the operator to perform a manual verification of the asset.
The operator should verify that:
If the asset association is missing or incorrect, the operator must manually link the file to the appropriate asset following the standard operational procedure.
For streaming recordings, this verification may not be necessary, as the asset association is typically created automatically a few seconds after the recording starts.
The Ingest Service is the component responsible for managing and writing the media data generated during a recording session. For this reason, it must remain running for the entire duration of the recording.
If the Ingest Service unexpectedly crashes, stops responding, or is manually restarted while a recording is in progress, the active recording cannot continue and will be immediately interrupted.
In this situation:
Unlike temporary connection losses involving other system components, the Ingest Service is directly responsible for creating and writing the media file. Therefore, an interruption of this service during recording prevents the file from being completed and saved correctly.
Important: The Ingest Service must always be running on the server hosting the recording channels. Operators and system administrators should avoid stopping or restarting the service while recordings are active and should promptly investigate any unexpected service failures to prevent data loss.