Skip to content

Inaccurate outcome when flushing replays #18316

Description

@billyvg

Description

In the _runFlush() method, we have a try/catch around a block of code that emits the following 2 outcomes: ratelimit_backoff and send_error.

However, within the try block we are throwing an unrelated exception when the session is too long and not attempted to be sent at all.

It would be nice if we could record this as a separate outcome so that we can use it to debug cases where a replay is not sent.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions