Troubleshooting and support
What to try when the AI loops on the same error, and what to send support.
Most issues resolve faster with a bit of context. Here is what helps.
What if the AI keeps looping on the same error?
Stop after three attempts and change the approach rather than trying a fourth time.
- Ask it to restore a checkpoint from before the change went sideways. The Checkpoint panel in your project on floot.com lists every checkpoint it saved, newest first, with a Restore on each. Next time, ask it to save a checkpoint before it tries something risky.
- Ask it to diagnose before it edits anything else. It can read files, run a typecheck and run your tests without changing a line.
- Ask it to read the backend logs first — it can pull them, including the published app's production logs.
- Contact support with your project URL.
What a loop costs
A loop spends build actions, not credits — and calls that fail or are cancelled never count at all. If a loop has eaten your daily actions, send us your project URL and we will look at what happened.
What details do you need to investigate an issue?
Share the full details of what you are seeing and your project link with live chat support. What you did, what you expected, and what actually happened covers most of it.
Can I send a screenshot to help debug?
Yes — and better still, use the Annotate tool in your project on floot.com to circle the problem area. That captures the screenshot and the context together. Share it with your assistant, which can open the annotation and see exactly what you circled. Screenshots in live chat are helpful too.
My published app looks different from the preview
Preview shows your latest changes; the published app shows the last version you published. Ask your assistant to publish again. On an app that is already live, publish_app publishes it again on the same URL.
You can also push it live yourself with the Publish button in your project on floot.com — see how preview and publishing work.