Our Genome Scan sender stopped delivering readouts this week, and nothing announced it. A direct probe found the real cause: the Supabase CLI login token was simply gone from the machine's keyring, so every queue read failed auth while the daemon kept trying. The good news is the design held — scans still land and store through the endpoint, which does not use that token, so no readout was lost. They sit in the queue waiting, and delivery resumes the moment the CLI is logged in again. The lesson: a silent auth loss looks exactly like a quiet day unless you probe it.
The recovery is the part worth noting: because scans are stored through an endpoint that does not use that token, no readout was lost, and delivery resumes as soon as the CLI is logged in again.
commentslikes