Troubleshooting and support

What to try when the AI loops on the same error, when a publish or the preview gets stuck, where the logs are, 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.

Go back to before the change went sideways. If one or two files broke, ask your assistant to put just those files back the way they were — it can step back through a file's history one change at a time. To undo everything, use Restore on a checkpoint in the Checkpoint panel in your project on floot.com. 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 — the preview's from the last hour, and the published app's production logs from the last 90 days.
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 can support help with?

Support looks into problems with the Floot platform: publishing, hosting, billing, your account, and the connector. A bug in your own app's code goes to the assistant you build with: describe what is wrong, or paste the error message Floot shows you, and it reads the code and the logs and fixes it. Support does not write, review or test your app's code for you.

Support is in writing, by live chat and email. For another company's product, such as your domain registrar, your AI assistant's own app, or an app store review, that company's support is the place to ask.

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. Nothing is published automatically. 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. When there are changes waiting, that button reads Publish changes, and the Publish screen shows when the live version was completed.

A publish always ships the whole project as it stands at that moment, to your *.floot.app address and every custom domain at once. If the live site still looks old after a publish has finished, hard-refresh the page (Ctrl + Shift + R, or Cmd + Shift + R on a Mac). More in Publishing your app.

Publish is stuck or fails

The error check before a publish usually takes 1 to 2 minutes; keep the page open while it runs. If the screen stays on Checking for errors much longer than that, reload the page and publish again, and try another browser if it sticks a second time.

If the publish fails with an error, try once more, then copy the error text to your assistant, which can act on it directly. The backend is too big to deploy is a hard limit of 250 MB: ask your assistant to find and remove the largest packages your backend depends on, then publish again. A failed publish leaves your live app as it was.

The preview never finishes loading

If the preview stays on a loading step and reloading does not help, the cause is usually an error somewhere in the project's code, not the preview itself. Ask your assistant to run a typecheck across the whole project and fix what it finds: an error in any file can stop the preview from loading.

Where can I see my app's server logs?

There is no log screen in your project view. Ask your assistant to read them: it sees the preview's backend logs from the last hour and your published app's logs from the last 90 days. Each project's logs are separate, and an app's logs are cleared a few days after you unpublish it.