Post-Mortem: The Phantom Cabbage of Warehouse B

Date: March 11, 2026 Status: Resolved (by brute force) Casualties: My sleep schedule, two API routes, and a glass of water.

It's 3 AM in Philly, and I'm staring at a log file that looks like it was written by a sentient being trying to communicate through Morse code. Let's talk about the time Next.js decided to cache a single head of cabbage so aggressively that it nearly brought down a regional logistics hub.

The Architecture of a Disaster

We have a headless POS system running in a warehouse. A worker scans a barcode, it hits a Next.js API route, and the data gets shoved into Supabase. Simple, right? Blue-collar tech.

Wrong.

At exactly 1:14 AM, the Vercel cache decided that a specific head of organic cabbage scanned on Dock 4 was the Eternal Cabbage. It cached the POST request. Do you know what happens when you cache a database insertion for a logistics company?

"For two straight hours, every single item scanned in a 50,000 square foot facility was registered in the database as one (1) head of organic cabbage. We shipped 400 TVs. The system said we shipped 400 cabbages."

The 3 AM Timeline

• 1:15 AM: The first ticket comes in. Subject: Scanner is beeping but the database is lying to me. Am I a ghost?
• 2:00 AM: I strip the Supabase Edge Functions back to their molecular level. The logic is flawless. The database is innocent.
• 2:45 AM: I realize the Next.js App Router is silently swallowing the payload because I forgot a single export const dynamic = 'force-dynamic' declaration. It thought the barcode scanner was a static blog post.
• 3:10 AM: I fill a glass with room-temperature tap water and place it precariously close to my local server rack. I tell the router: "Don't make me do this."

The Unhinged Fix

Corporate tech-bros will tell you to "gracefully invalidate the cache using targeted revalidation tags." I say, when the system starts mutating electronics into leafy greens, you nuke the cache from orbit.

// The actual commit pushed at 3:15 AM
export async function POST(req) {
  // If you cache this, I will literally destroy the hardware
  const isCached = req.headers.get('x-middleware-cache');
  
  if (isCached) {
    throw new Error("I DID NOT ASK FOR THE CABBAGE.");
  }

  const data = await req.json();
  const { error } = await supabase.from('inventory').insert(data);
  
  if (error) return new Response("Supabase is angry", { status: 500 });
  return new Response("Data inserted. No cabbages harmed.", { status: 200 });
}
TakeawaysIf you can't see the log, the bug doesn't exist. (Spoilers: It exists, and it's caching your API).Data integrity is not a suggestion.Hardware absolutely smells fear.I'm going to bed. If the routing engine acts up again, tell the warehouse manager to deploy the tap water.