Know when your Lovable app stops working

These come from Lovable's own docs and from failures we've written guides for. Under each one, “Heedza sees this” means the problem stops a page from opening or removes its form, so you get an alert. Heedza only sees what a visitor sees before logging in, so it can’t see problems that happen after a form is sent.

1. The live site isn't what you see in the editor. Lovable's docs: "The published site is a snapshot. Changes you make after publishing don't affect the live site until you open the Publish dialog again and click Publish changes" (Lovable: Hosting). A fix can be done in the editor and still be missing live, and the reverse: a broken edit goes live with the next publish. Heedza sees this.
2. A build error stops publishing. If your latest changes failed to build, the Publish dialog shows Try to fix instead of the publish button (Lovable: Publish). Heedza sees this.
3. The backend pauses. Lovable says that when you run out of credits, "apps that rely on the backend or AI features can pause until credits are available again", and a paused backend "may not restart by itself" (the docs point to More → Cloud → Overview → Wake up) (Lovable: Hosting). Your pages may still open while log-in and data don't. Heedza sees this.
4. The site gets unpublished. On the Free plan, "Lovable may have unpublished it for inactivity" (Lovable: Hosting). Heedza sees this.
5. The custom domain isn't Live. Lovable's checklist says to check that the domain's status in Project → Settings → Domains is Live (Lovable: Hosting). Heedza sees this.
6. Google sign-in fails on a new domain. With your own Google credentials, connecting your own domain later adds a new address for Google to send people back to after sign-in, and it isn't selected yet. Until you add it in Google Cloud and select it in Lovable, "Google sign-in fails on the new domain with a redirect URI mismatch error" (Lovable: Google authentication). Heedza can’t see this.
7. Log-in works in preview but not after publish, usually the sign-in address settings. See our guide: Lovable login works in preview but not after publish? Heedza can’t see this if the log-in form still shows, because it never logs in. It sees it if the log-in page stops opening.
8. Payments don't work live. See Lovable Stripe payments not working? Heedza can’t see this.
9. Emails only reach you. Resend's test sender only delivers to your own address: Resend "You can only send testing emails…" Heedza can’t see this.

Heedza works from the outside, on your public web address. There's nothing to install.

• Your key pages. We open your home page the way a visitor does, follow its links to your sign-up, log-in and payment pages, and check on a schedule that each one opens and shows its form or Pay button.
• Security checks. The free scan looks for secret keys in your page code and .env or .git files anyone can open.
• Alerts. When a check fails, you get an alert (by email, or on paid plans also Slack, Telegram or a webhook (we send the alert to a web address you choose; for developers)) with a picture of the page and a fix written for Lovable, ready to paste into the Lovable chat.

It never fills in forms, never logs in, never types a card number and never clicks Pay. So it can't tell you whether a log-in, email or payment works after the button is pressed.

It works the same for any vibe-coded app, whichever AI tool made it. Build Lovable apps for clients? See Heedza for agencies: up to 30 client sites, with white label client reports and status pages on Business.