All field notesField note 02 / 05 · details changed under NDA
Fixed · Critical

When the error message lies

Users were told their connection dropped. It was a server-side rejection all along. Now the UI tells the truth.

  1. 01

    Symptom

    Users on stable connections got stuck on “Waiting to reconnect…” right after uploading, and could not continue.

  2. 02

    Root cause

    The UI treated every failed upload as a network drop. The real failure was a server-side rejection of large files.

  3. 03

    Fix

    Fixed the upload path for large files, and split server errors from connectivity errors so the screen tells the truth.

  4. 04

    Impact

    Users finish their flow again, and failures say what actually went wrong.

Debug log

  1. $reproduce on a stable connection to rule out the network
  2. $network panel: the upload was rejected, not lost
  3. $fix the upload path for large files
  4. $stop mapping server errors to the reconnect screen
  5. ✓resolved

A thousand welcomes

What's the next big idea?