The AI says it fixed it, but the error is still there. Now what?
Published
What does this error usually look like?
You describe the problem, the AI replies that it fixed it, you test and everything is the same. Sometimes it tries the same fix several times in a row.
What should you paste into the AI?
Copy the text below, replace what’s in brackets and send it in the chat of the tool you’re using.
The problem is exactly the same after your last fix.
What I did to test: [step-by-step test].
What happened: [the result].
Error message, if any: [paste it here].
Don't try the same solution again. First explain what you think is causing the problem and what other causes are possible. Then try a different approach.Why does this happen?
The AI doesn’t test the app the way you do. It changes the code and assumes the change solved the problem. When the assumption is wrong, it tends to repeat the same reasoning and reach the same fix.
Asking it to list other possible causes before acting breaks that cycle. It also helps to say exactly how you tested, because sometimes the problem only shows up on a specific path.
When should you stop and go back a version?
If the app is worse than before or you no longer know what works, go back through the version history. Then ask for the original change again, split into parts. Doing only the first part, testing it, and then asking for the second usually works better.
Frequently asked questions
Does each attempt use credits?
In tools with a usage limit, usually yes. That's why it's worth stopping after two or three identical attempts instead of insisting.
Does starting the project over fix it?
Sometimes, but it's the last option. Going back to an earlier version that worked is usually faster and keeps what was already good.