When it breaks, don't panic
Diagnose and safely fix the failures AI-built and no-code apps commonly produce, and know when a fix is beyond you.
Get started: Start: fix it without a developer · Browse the error library
In plain English
Most breakages have a calm, safe path back: figure out what changed, back up, and try small, reversible steps. This hub shows you how, and when to stop and get help.
Back up before you change anything — Before you touch a broken app, make a backup you can restore. If a problem involves lost data, payments, or logins, get a professional; some mistakes cannot be undone.
Who this is for
- Anyone staring at an app that suddenly stopped working
- People whose AI tool can no longer fix its own bug
- Builders who are afraid to touch their app in case it breaks more
A calm first response
- What changed? — Note the last thing you or the AI did. Most breaks trace back to a recent change.
- Back up — Save a copy of your app and data before you try anything.
- Revert if you can — Undo the last change and see if that restores things.
- Check status — Confirm your tools and hosting are not simply down.
- Diagnose safely — Read the error, search it, and try small reversible fixes.
- Know when to get help — If it touches data loss, payments, or auth, bring in a professional.
Guides in this hub
- Fix Your AI-Built App Without a Developer — the complete first-response guide
- How to Read an Error Message Without a Developer
- Why the AI That Built Your App Can't Fix It Anymore
- The Safe-Change Workflow — back up, small change, test, keep or revert
- Common AI and No-Code Failures
- Fix It, Direct the AI, or Hire a Developer — a decision guide
Where to go next
The error & fix library
Search common symptoms and what they mean.
Secure what you shipped
Some breakages are security issues in disguise.
Direct AI well
Learn to give the AI changes that fix without regressions.
Get new fixes as they land
If your symptom is not listed, the debugging workflow on this page still applies: preserve the exact message, reproduce it, and test one reversible step at a time.
Debug FAQ
My app broke and I did not change anything. Now what?
Something usually changed, even if it was an automatic update or a tool outage. Check status pages, then follow the first-response steps and revert recent changes.
Can I just ask the AI to fix it?
Sometimes, but the AI often loses track of your app over time. "Why the AI Can't Fix Your App Anymore" explains why and how to give it what it needs.
How do I avoid making things worse?
Back up first, change one small thing at a time, and test after each step so you can undo it. That is the safe-change workflow.
When should I hire someone?
When a problem risks losing data, or touches payments or logins, or when you have tried the safe steps and are still stuck. The decision guide gives clear thresholds.
Do you have a page for my exact error?
Start with "How to Read an Error Message" and "Common Failures," and check the library for your symptom.
Kodbe is an independent publication about maintaining and owning software you built with AI or no-code tools. It is not affiliated with, endorsed by, or connected to Kodbe Inc (the Albany, GA educational nonprofit), Kodobe, Kodable, or Kodu.