Work in progressThis site is being built in public — expect rough edges, missing screenshots and drops that change under you.

← the log

Your offline token expires mid-job, and the 401 arrives in four different shapes

Drop 007·In progress·Remix, Admin API, Auth, Background jobs

An offline access token lives one hour, and every public app has to be on expiring tokens by January 2027. So background work will meet an expired token mid-run — and the 401 that comes back is not one error. It arrives in four different shapes. Three of them you should retry. The fourth is App Bridge's re-auth signal, and catching it breaks sign-in for every merchant you have, silently.

What it covers

  • The four shapes a token failure arrives in, and how to tell them apart
  • Why the calling context is the discriminator, not the error class
  • A retry that was documented as sufficient, and the premise it got wrong
  • How to force an expired token on purpose, so you can test any of this