Incident-pattern library

The failures that actually take no-code apps down

An incident pattern is a recurring production failure described from the symptom inward: what you see, the root cause in plain English, the steps that fix it, and the check that catches it automatically next time. Every pattern here comes from incidents diagnosed on real no-code and AI-built apps — anonymized and verified — so you can fix the problem now and stop rediscovering it later.

Platform
Flow

15 of 15 patterns

  • Supabase
  • Lovable
  • Bubble
  • Any stack
  • Auth & login
  • Email delivery

Magic-link login emails not arriving

A user types their email, the app says "check your inbox", and nothing arrives — not even in spam. It often works for your own address but fails for real users.

  • Lovable
  • Bolt
  • Bubble
  • Any stack
  • Checkout & payments

Checkout page loads blank after a deploy

The homepage works and uptime says everything is green, but the checkout or payment page renders blank, half-empty, or stuck on a spinner — usually starting right after a deploy.

  • Bubble
  • Lovable
  • Bolt
  • Checkout & payments
  • Webhooks

Stripe test keys shipped to production

Checkout appears to work — sometimes a test card even succeeds — but no real payouts arrive, real cards get declined, or the Stripe dashboard shows zero live activity while your app claims sales.

  • Bubble
  • Supabase
  • Any stack
  • Webhooks

Webhook returns 200 but nothing happens

The sender's dashboard (Stripe, Typeform, GitHub…) shows every delivery succeeding with a 200 — but the order isn't created, the record isn't updated, the notification never goes out.

  • Supabase
  • Lovable
  • Bolt
  • Auth & login

Supabase queries return empty after enabling RLS

Lists and dashboards that worked in development render empty in production. The table has rows in the Supabase dashboard, the network tab shows 200 responses — but every select comes back with zero rows.

  • Supabase
  • Lovable
  • Bolt
  • Webhooks
  • Scheduled jobs

Supabase: "Max client connections reached"

Under load — or seemingly at random — requests start failing with "Max client connections reached" or timeouts. A restart clears it, traffic brings it back, and the database itself doesn't look busy.

  • Bubble
  • Supabase
  • Replit
  • Any stack
  • Scheduled jobs

Scheduled job stopped running and nobody noticed

Digests stop sending, syncs drift stale, cleanup never runs — and you find out days later from a customer. The scheduler dashboard shows nothing obviously wrong.

  • Any stack
  • Bubble
  • Webflow
  • Email delivery

Transactional emails land in spam

Receipts, password resets, magic links, or notifications reach some users' spam folders — or vanish entirely. Deliverability quietly worsens as you send more.

  • Webflow
  • Bubble
  • Any stack
  • Forms & leads
  • Email delivery

Form shows success but no lead arrives

Visitors fill in the form and see the success message, but nothing lands in your inbox, CRM, or sheet. You usually discover it by accident — days or weeks of leads are simply gone.

  • Supabase
  • Bubble
  • Any stack
  • Auth & login
  • DNS & SSL

OAuth login broke after a domain change: redirect_uri_mismatch

"Sign in with Google/GitHub" stopped working right after moving to a custom domain (or adding www, or switching to https). The provider shows redirect_uri_mismatch, or users bounce back logged out.

  • Webflow
  • Bubble
  • Any stack
  • DNS & SSL

DNS cutover left the site half-broken

After moving hosts or domains, behavior depends on who's looking: some visitors get the new site, some the old one, some a certificate warning or a hosting provider's default page. It "works on your machine" while support tickets disagree.

  • Any stack
  • Webflow
  • Replit
  • DNS & SSL

SSL certificate expired on an API subdomain

The main site is fine, but api.yourdomain.com (or app., or admin.) suddenly throws certificate errors — browsers show warnings and every API client starts hard-failing at once.

  • Replit
  • DNS & SSL
  • Scheduled jobs

Replit app keeps going to sleep on its custom domain

Your Replit-hosted app is unreachable or painfully slow on the first visit after a quiet period — then fine. Webhooks time out, background tasks miss their windows, and it always works once you go look.

Newsletter

Get new incident patterns as we publish them

One email when new failure patterns, fixes, and monitoring recipes for no-code and AI-built apps land. No fluff, unsubscribe any time.

Double opt-in. One-click unsubscribe. No spam, ever.