Problems creating raw-tracks recordings

What to do

• Check whether you use Daily Recording/Live Streaming. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 7h 33m it lasted.

  Anything that failed between 2023-01-18 20:54 UTC and 2023-01-19 04:27 UTC may need a replay.

• Subscribe to Daily's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=daily works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Daily 5

1. investigatingJan 18, 2023, 8:54 PM UTC

   We're investigating reports of errors from customers trying to create "raw-tracks" recordings.

   provider

2. identifiedJan 18, 2023, 9:27 PM UTC

   We've confirmed an issue preventing the creation of raw-tracks recordings. Other recording types are unaffected, including "cloud" recordings to your own S3 bucket. If you need to record an important call during this incident, you can change the enable_recording property on your domain, room, or meeting token to cloud to make a cloud recording.

   provider

3. identifiedJan 19, 2023, 2:18 AM UTC

   We're in the process of deploying updates to resolve this issue. We'll resolve the incident as soon as the fix is live in production.

   provider

4. monitoringJan 19, 2023, 2:32 AM UTC

   We've deployed new call servers and recording infrastructure to resolve the issue. You should be able to start a raw-tracks recording from any call session that started on or after approximately 02:15 UTC. Existing long-running call sessions may still be running on older call server instances. Those sessions may still experience errors with raw-tracks recordings. Those sessions will automatically move to new call server instances within the next few hours as part of our normal deploy process. We'll resolve this incident when all of the old call server instances have been retired and operations are back to normal.

   provider

5. resolvedJan 19, 2023, 4:27 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.