When an error occurs, we capture and upload a replay to Sentry. This means that we need to buffer the replay events and only upload on an error event. We need to place an upper bound on the events we buffer, in order to do so, we configure rrweb to checkout the full DOM on a time interval (alternatively we could do it based on an event count, or replay size). Otherwise end users will face memory issues having to store all of the incremental updates.

After an error occurs, we should continue to record the session. The SDK currently is easily setup to continue recording forever, however we may want to limit the amount of time after the error. The important parts of the replay should be what immediately happens before and after the error.
- If we record only up to a specific timeframe after the error happens, what should we do if a new error occurs? Should it always become a new session? Should it be part of the previous replay (given that it happens within the session lifetime).