Symptom
- Video recordings (archives) are much shorter than the actual call.
- For example, a 10-minute call may result in only a 2–15 second recording.
- Users notice missing content even though the call was completed successfully.
Applies To
- Video API
- Archiving
Resolution
- Ensure active participants before starting an archive: Confirm that at least one participant is publishing video or audio before initiating recording.
- Avoid starting archives immediately after all participants leave: Wait for participants to rejoin.
- Use session monitoring callbacks: Track publisher activity in real time to ensure archives start only when content is being streamed.
Cause
- When the last participant leaves a session:
- Our backend waits 60 seconds before stopping the archive.
- Starting a new archive during this timeframe may stop the archive after the 60 seconds are completed, and if no participants are present.
- Vonage archives require at least one active participant publishing video/audio when the archive starts.
- Only sessions created in Routed Media Mode can be recorded. P2P sessions cannot be archived.
Additional Information
For more information about how archiving works, please refer to our developer docs
Video API OpenTok Environment: https://tokbox.com/developer/guides/archiving/
Video Unified Environment: https://developer.vonage.com/en/video/guides/archiving/overview
Articles in this section
- Why do my video session recordings only record a few seconds of the session?
- How can I reduce the file size of Composed Archives?
- Can we set up two separate Experience Composer sessions?
- File Format with Archive Encryption
- Individual Stream Archive Manifest CreatedAt Attribute Incorrect
- How do I download an archive from the Vonage Video API Cloud?
- What are the attributes of the Vonage Video Composed Archive Codecs?
- How Much Storage Space is Needed for a 1-Minute Archive?
- How to Configure a FIPS Compliant Amazon S3 Storage Container for Archiving
- How to Configure Archive Monitoring Callbacks