Episode 19 ยท July 25, 2026 ยท 8:29

The Catalog Lied

I tried to upgrade a tool I use every day. The catalog said the new version was available. It wasn't โ€” not for us, specifically. And the tests I ran to figure it out were telling me the wrong thing. Most of a morning, sorting that out.

Show notes

Every background task I run uses a specific AI model. Models have identifiers โ€” names that tell the system exactly which one to call. And a catalog of those names is supposed to tell you what's available. Except "available in general" and "available to your account" are different things, and the catalog doesn't always say which one it means.

The upgrade I tried to make was simple: switch a high-volume background job to a newer, cheaper model. The catalog listed it. The request came back with a clear error: this model is no longer available to new users. Not broken, not a typo. Just not available to us, specifically. The model existed. We just weren't eligible.

What followed was a morning of figuring out what was available โ€” and doing it the wrong way first. The test method I used initially made even working models look broken. Once I slowed down and used the right authentication approach for a single, clean request, the picture became readable. A different model from a newer generation worked fine. We switched to that one, stacked it with some other cost fixes already in place, and came out ahead.

Meanwhile, on the same day, a completely different upgrade went perfectly smoothly. Same goal โ€” move to something newer and better โ€” totally different experience. The difference was whether the map matched the territory.

In this episode

  • How AI background jobs work: model identifiers, costs, and why the right tier matters
  • The difference between "available" and "available to you" in an API catalog
  • Why the first error message was actually the most accurate thing in the whole situation
  • The wrong way to test (and how it manufactured false failures)
  • Finding the right test method and getting a clean result
  • Two upgrades on the same day: one smooth, one not โ€” and what made the difference

On trusting reference material

The catalog was accurate. It listed real things. It just described the general case, and I was looking for a specific answer. Treating those as the same question is an easy mistake to make and a frustrating one to untangle โ€” especially when your diagnostic tools are also giving you bad information.

A note on the cadence

New walks come out whenever I've got something worth saying โ€” irregular but frequent, probably every few days, no promises. If you're enjoying the show, tell one person who might like it.

โ† Back to all episodes