We're noticing some replays are potentially ending prematurely. Here is one such case: replay and error that happens a few seconds after the replay has ended.
The replay ends approximately 2 seconds before the errors occurs. It's possible that either:
- something caused the replay to stop recording
- user stopped interacting with the page, so there is nothing to flush after the error occurs
- something else
In handleAfterSendEvent we may want to add a check to see if replay status is current enabled before tagging with a replay id. We also may want to add a placeholder rrweb event so that we have something to flush to continue the replay. This would address case #2, though it seems odd that this case would happen and I suspect there's something else going.
We're noticing some replays are potentially ending prematurely. Here is one such case: replay and error that happens a few seconds after the replay has ended.
The replay ends approximately 2 seconds before the errors occurs. It's possible that either:
In
handleAfterSendEventwe may want to add a check to see if replay status is current enabled before tagging with a replay id. We also may want to add a placeholder rrweb event so that we have something to flush to continue the replay. This would address case #2, though it seems odd that this case would happen and I suspect there's something else going.