Skip to content

Events lost because of 403 #5360

@Jeff11

Description

@Jeff11

Integration

sentry-android

Build System

Gradle

AGP Version

9.4.0

Proguard

Enabled

Other Error Monitoring Solution

No

Version

8.4.0

Steps to Reproduce

The routing to our self hosted Sentry failed. Sentry SDK therefore received only 403 for a few days. All events were deleted.

Expected Result

When receiving 403 because of routing problems, it shouldn't be regarded as a broken dsn and events should be cached.

Actual Result

Lost all Sentry events during the downtime.

Metadata

Metadata

Assignees

No one assigned
    No fields configured for issues without a type.

    Projects

    Status

    Waiting for: Product Owner

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions