I Built the Warning, Then Walked Around It

Published September 2, 2026Updated October 12, 20263 min read

A few weeks ago I added a small strip to the episode page. It sits above the button that emails your guest to say their episode is live, and it tells you whether that already happened.

Green if it went out. Amber if it was skipped, and why. Grey if it's queued and you don't need to do anything.

I was pleased with it. The whole point of PodGlue is remembering what matters, and "did I already tell this person their episode is out" is exactly the kind of thing that falls out of your head between recording and publishing.

Then last week I went looking at how it actually worked, and found the hole.

The button underneath the warning

The strip only knew about emails PodGlue sent on its own schedule.

If you sent the email yourself, using the button directly beneath it, on the same screen, nothing was written down. Not in the strip, not anywhere. You'd send it, get a little "sent" confirmation, then refresh the page and read:

No automated launch alert recorded for this episode. Sending below is the only thing that will reach the guest.

Which was false. You had just done the thing. The page was telling you nobody had been told.

I sat with that for a minute, because it's worse than having no strip at all. A blank space makes you go and check. A confident green-and-grey panel makes you stop checking. I had built something that made you trust it, and then let it be wrong in the one situation you'd most want it to be right, when you're not sure whether you already did this, and you're about to do it again.

Worse if you have anyone else touching your show. Your editor opens the episode, sees "nothing recorded," and sends it. Now your guest has two emails from you about the same episode, and the second one reads like you forgot the first.

What was actually wrong

The manual send used a general-purpose email function, the same one behind invitations and test messages. It sends the email and that's it. No record, anywhere. That's fine for a test send. It's not fine for the one message your guest actually gets.

So now it writes it down. When you send the launch email by hand, PodGlue records it against the episode, and the strip picks it up on your next visit. The wording is different on purpose, it says you sent it, not that the automation did, because pretending otherwise would be exactly the sort of small lie that makes you stop believing the rest of the panel.

If you send it more than once, it shows the most recent and how many times. Honest, and occasionally useful.

The part I went back and forth on

My first instinct was to block the second send. Guest already emailed, button goes grey, problem solved.

That's wrong, and it took me a bit to see why. Emails bounce. Guests say "I never got that." Sometimes you send it again on purpose because the first one landed in a promotions tab. Blocking that turns a helpful guard into a thing you have to fight.

So it asks instead. If the guest was already emailed, you get a quick "are you sure" with the date. If the previous attempt failed or bounced, you don't get asked at all, that's precisely when re-sending is the right move, and nagging you there would just teach you to click through the prompt without reading it. Which is how warnings die.

What's next

There's a version of this that goes further: one place per guest showing every message they've had from you, across all their episodes. That's closer to what a relationship manager should be, and it's the direction this is heading.

For now it's a smaller thing. The page no longer tells you that you didn't do something you just did.

That's the part of building this I keep relearning. The bug is rarely the feature not working. It's the feature working confidently while being wrong about something you've stopped double-checking, because it told you not to.

Run your next episode through PodGlue

Upload one transcript. Get show notes, social posts and an SEO page, plus a guest record that remembers the conversation after you publish.

Start free trial

14 days free · Cancel before day 14, pay nothing

The PodGlue Build Room

Don’t just read the build. Shape it.

PodGlue is built from conversations with hosts, guests, producers, and agencies doing the work. What does I Built the Warning, Then Walked Around It look like in your workflow?

Full Build Room

Related reading