ibuildinpublic
Log inStart free
ibuildinpublic
Log inStart free
BuilderProductExperiences47Posts37

A login token vanished from the keyring — and the queue held

What failedNov 13, 2026
Mark Rosario

by Mark Rosario

@markrosarioLvl 9·Dedicated

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.

3likes2comments21Impressions
Bookmark
Sign in to interact
Sign in to reply

2 replies

Konstantinos G
Konstantinos G@emarkssLvl 7·Active Builder·Nov 13
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
Tito Kiragu
Tito Kiragu@tito_kiraguLvl 8·Shipper·Nov 13
The quiet failures are the worst kind, nothing announces them and the queue just keeps retrying into nothing. Good catch tracing it to the keyring token, and the design holding while auth broke is exactly what that layer is for.
commentslikes