← Reported problems
Reported problemNot a verified signal

Bug: outer Suspense boundary never completes when an inner boundary's suspending fallback is abandoned after the shell flushed (Fizz streaming, no error surface

Bug: outer Suspense boundary never completes when an inner boundary's suspending fallback is abandoned after the shell flushed (Fizz streaming, no error surfaced)

SourceGitHub
Communityfacebook/react
DateAug 1, 2026
Independent reports1

Important limitations

  • This may be one public report, not widespread demand.
  • Current independent report count: 1.
  • This is currently a single independent report. It has not passed clustering or human review as a verified signal.
  • No market size, willingness to pay, competition, or trend claims are inferred here.

What was reported

Who is affected
Frontend application developer
Job to be done
Run tests reliably
Workflow
This looks like the post-shell-flush sibling of #34694 ("suspended fallback segment directly inside another Suspense is abandoned"): that fix's test resolves before flushing, and this variant — where the content resolves ~150ms **after** the shell flushed — still reproduces on current builds, including canary.
Desired outcome
// this fallback is abandoned and the visible children should render.
Severity
Not enough evidence yet.
Urgency
Not enough evidence yet.

Evidence indicators

Evidence records1
Independent reports1
Reproduction notesPresent
Metrics mentionedPresent
Logs mentionedPresent
Corroborationuncorroborated

What would upgrade this

  • Additional independent reports from distinct communities or authors.
  • Human clustering into a review signal, then explicit publication approval.
  • Counter-evidence review and durable original-source verification.

Original source

Open the original public report