
The Missing Key That Ate Three Days of Bookings
Bianca's booking died at ServiceWriter's door — the trace found a missing encryption key, the fix is green, and the merge is waiting on one tap.
Share this episode
Every share includes a caption, call to action, and hashtags — just pick your platform.
🎙️ The Missing Key That Ate Three Days of Bookings Bianca's booking died at ServiceWriter's door — the trace found a missing encryption key, the fix is green, and the m... Press play and listen 👇
https://momsoilchange.com/podcast/the-missing-key-that-ate-three-days-of-bookings-2026-11-21
#MobileOilChange #momsoilchange #servicewriter #AutoIndustry #SmallBusiness #PhillyBusiness
LinkedIn doesn't accept pre-filled text — we copy the caption for you automatically.
Full Transcript
Tyreese: Good evening from the shop. It is Saturday, November twenty-first, and this is The Build Log. What got built, what broke, and what the proof says. No evidence, no green.
Tyreese: Here is the headline. Yesterday Bianca Dean called my phone agent and booked a full synthetic oil change for eleven in the morning. The agent confirmed it, gave her a reference code, and five seconds later handed it to ServiceWriter. ServiceWriter answered with a five hundred error. Twice. Her booking never crossed over.
Tyreese: So today we traced it. Not guessed, traced. The delivery record is right there. The booking exists, the pairing exists, the mirror is switched on, and the built-in calendar path is wired. ScreenMyCalls did its job. The failure is on ServiceWriter's side, at the front door of its intake, in the stage that checks the pairing credential.
Tyreese: Here is the part that stings. Three days ago, pull request three forty-six moved the pairing secret into an encrypted store. Every request now has to decrypt that secret on the way in. But production never had the encryption key, not on any target. So every authenticated request since then has thrown at decryption and died with a five hundred. The tests never caught it because every test set the key up front. The missing-key state had zero coverage. That is how three days of bookings quietly never crossed over.
Tyreese: Why would nobody check before shipping that? That is terrible process. So we made a new standing rule on the spot. Any change that touches how production credentials or config are read has to verify the production target actually carries the required keys, and carry a test for the missing case, not just the happy path. Green CI alone does not count for those changes anymore.
Tyreese: Now the good news. The fix is written. Pull request three seventy-six hardens the pairing secret load. If the encrypted store cannot be read, it falls back to the legacy secret, and if decryption fails with no legacy secret, it fails closed with a clean four-oh-one instead of a five hundred. Every failure now names the stage that broke. The regression tests include the unconfigured key case. All three thousand eight hundred and seventy-four tests passed, type checks and smoke tests passed, and code review came back clean. The pull request is fully green and ready to merge.
Tyreese: But it is not merged. The merge was fired, the approval sat for thirty minutes, and it expired. So the fix sits there, green, waiting on one tap while I work. Once it merges and deploys, we probe the intake, re-enable the sweep, and Bianca's booking crosses on its third and final attempt, no duplicate. Fix first, then sweep.
Tyreese: The sweep taught us a second thing. It has been stalled since the database outage on November nineteenth. Its fifteen-minute cron trigger was switched off after thirteen straight failures and never switched back on. A manual trigger masked it. That is good news right now, because nothing can fire that third attempt on its own. But a manual check is not a recovery.
Tyreese: Now Square. This morning I made a call. Square is working, ServiceWriter is unproven, so let us point the phone agent at Square and take it to the moon. We went to flip the switch, and the live database said the Square connection table has zero rows. Disconnected, not expired. The last live Square booking was November seventeenth. So the pivot is real, but the switch is blocked on one step only I can do. Reconnect Square in the console, fresh OAuth, then we verify the sync, flip the backend, and prove it with one test call.
Tyreese: We also finished the study of how the website pushes bookings into ServiceWriter. There is no single push. The marketing links send people to ServiceWriter's own hosted booking page, so the booking is born in ServiceWriter and nothing is pushed. The website wizard writes into a different backend, and its push into ServiceWriter never verifiably fired. And neither path can carry an add-on. The wizard sends one service per vehicle job, no add-on field. The hosted page ignores offer codes. That is the seam that lost Aaron Bado's wiper blades.
Tyreese: Speaking of Aaron, that story closed today too, and it closed with a ghost. Aaron paid two hundred and twenty-one dollars. The two hundred and seventy-one dollar item sitting pending in ServiceWriter has no charge behind it in Stripe. No payment intent, nothing pending. We went into ServiceWriter to cancel it, and there is no cancel button. No void, no delete, no refund. Its menu only offers send invoice, send payment link, or record manual payment. So the ghost cannot be cancelled from the screen. It needs a behind-the-scenes cleanup, and I told the team, cancel that joint, he already paid.
Tyreese: What else shipped today. The daily product post went out on LinkedIn for Fleet-Mail, the single auditable system of record for fleet work. Pull request one ninety-nine, the customer signature capture in the tech app, two thousand and sixty-seven tests green, pushed and waiting on my merge tap. The morning briefing went out too, on Pennzoil losing its dexos license, and today's hooks are seeded, with Business versus Job, eight hundred and eighty thousand likes, as the pick. But I will be straight with you. The blog pages for this week's briefings are four-oh-four on the live site because fourteen commits were never pushed. I told the team today, push it, we have full access to everything.
Tyreese: So what is next. First, the merge tap on pull request three seventy-six, then deploy, probe the intake, re-enable the sweep, and Bianca's booking crosses. Second, I reconnect Square and we prove the agent can book there. Third, the ten D L C registration failed again, because the brand industry value is not one Telnyx accepts, so that re-file is on the list. And fourth, the real capture. No real photo or video from the live Job Capture app on a real job made it into ScreenCut today. The gate is a real job, and it is still unproven.
Tyreese: That is the day. A booking died at the door over a missing key nobody checked for. The fix is green, waiting on one tap. Square is a reconnect away. And the rule that comes out of it is the one I am keeping. No evidence, no green. Not on a merge, not on a booking, not on a promise. I will see you tomorrow.
New episodes every weekday. Subscribe via RSS to get them in your podcatcher.
Book Your Oil Change