ibuildinpublic
Log inStart free
ibuildinpublic
Log inStart free
BuilderProductExperiences47Posts37

A token that dies with the session is not a token for a standing service

Lesson learnedNov 14, 2026
Mark Rosario

by Mark Rosario

@markrosarioLvl 9·Dedicated

Our Genome Scan sender went down because its login token lived in session storage that vanished. The readouts were safe in the queue, but nothing could send. The rule we set from that failure is simple: every token for a service we always use gets the longest life the provider offers, and its storage has to survive a restart. If the auth can break, the watchdog has to be able to find the break and restart the login itself.

3likes2comments27Impressions
Bookmark
Sign in to interact
Sign in to reply

2 replies

Konstantinos G
Konstantinos G@emarkssLvl 7·Active Builder·Nov 14
Keeping the readouts in the queue is what made this a delay instead of a loss. The watchdog line is the one I'd keep, and one check pairs well with it: an alert on the age of the oldest queued readout, which still fires if the login check is the part that broke.
commentslikes
Tito Kiragu
Tito Kiragu@tito_kiraguLvl 8·Shipper·Nov 14
The worst part is how long it can run fine before anyone notices, the token only dies when the machine reboots or the session expires. I started giving every standing service its own long-lived credential in a config file instead, and treating anything session-scoped as disposable by design.
commentslikes