Skip to content

Streaming fetch API calls are completely absent from the network tab #20714

New issue
New issue
Closed
#20722
Closed
Streaming fetch API calls are completely absent from the network tab#20714
#20722
Assignees
nicohrubec
Labels
BugReplays

Description

@dalnoki
dalnoki
opened on Apr 28, 2026

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Certain API calls are completely absent from the Replay network tab. Not just missing body or headers, but no entry at all. Other API calls in the same session appear correctly. The absent calls are confirmed as having been made during the session via independent logging and Sentry Logs, ruling out that they simply didn't fire. Additional details in the Linear ticket.

Expected Result

The request should appear in the Replay network tab with at minimum its URL, method, status code, and duration, even if the response body cannot be captured.

Actual Result

The request does not appear in the Replay network tab at all.

Product Area

Replays

Link

No response

DSN

No response

Version

No response

Activity

  1. linear-code commented on Apr 28, 2026

    @linear-code
    linear-codeBot
    on Apr 28, 2026 – with Linear Code

    ENG-7541

    JS-2374

  2. getsantry commented on Apr 28, 2026

    @getsantry
    getsantryBot
    on Apr 28, 2026

    Auto-routing to @getsentry/product-owners-replays for triage ⏲️

  3. getsantry
    added
    Waiting for: Product Owner
    on Apr 28, 2026
  4. getsantry
    added this to GitHub Issues with 👀 3on Apr 28, 2026
  5. getsantry
    moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on Apr 28, 2026
  6. linear-code
    added
    Bug
    Replays
    on Apr 28, 2026

  7. bcoe commented on Apr 30, 2026

    @bcoe
    bcoe
    on Apr 30, 2026
    Member

    I've added this issue to the replay team's backlog for triage, we will be digging into it soon.

  8. getsantry
    removed
    Waiting for: Product Owner
    on Apr 30, 2026
  9. getsantry
    moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3on Apr 30, 2026
  10. nsdeschenes
    transferred this issue fromgetsentry/sentryon May 7, 2026
  11. getsantry
    added
    Waiting for: Product Owner
    on May 7, 2026
  12. getsantry
    moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on May 7, 2026
  13. nicohrubec
    self-assigned this
    on May 8, 2026
  14. nicohrubec
    moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3on May 8, 2026
  15. nicohrubec
    removed
    Waiting for: Product Owner
    on May 8, 2026
  16. nicohrubec
    closed this as completedin #20722on May 11, 2026
  17. nicohrubec
    added a commit that references this issue on May 11, 2026

    fix(replay): Capture aborted/errored fetch requests in replay network…

    862359b

  18. nicohrubec commented on May 11, 2026

    @nicohrubec
    nicohrubec
    on May 11, 2026
    Member

    Fix is merged, should go out this week with the next release and then this should be resolved.

  19. github-actions commented on May 12, 2026

    @github-actions
    github-actionsBot
    on May 12, 2026 – with GitHub Actions
    Contributor

    A PR closing this issue has just been released 🚀

    This issue was referenced by PR #20722, which was included in the 10.53.0 release.

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

Metadata

Metadata

Assignees

Labels

BugReplays

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions