Agents

Troubleshooting

Common issues you might run into when using Buildprint agents, and how to resolve them.

Buildprint didn't build what I wanted

If the agent made changes that don't match what you had in mind, the fastest fix is to start over with a clearer prompt:

  1. Restore to your last savepoint to undo the agent's changes.

  2. Think about what was unclear — was the prompt too vague? Did it leave room for interpretation?

  3. Start a new conversation with a more specific prompt that describes exactly what you want.

Trying to get the agent to fix its own mistakes in the same conversation usually leads to more issues. A fresh start with a better prompt is almost always more effective.

Buildprint created issues in the editor

Buildprint cannot see Bubble's issue checker, so it may introduce errors it doesn't know about. For small, isolated issues, the easiest fix is to correct them yourself in the Bubble editor and ask Buildprint to resync so it can view your changes.

If the issues are significant and wide-ranging — affecting multiple workflows or data types — it's better to restore to a savepoint and start again with a narrower prompt. Attempting to patch many scattered issues usually takes longer than just redoing the work cleanly.

Buildprint, like any other human developer, is not perfect. Issues will be created sometimes, which is why it's important to review its work carefully.

Buildprint can't see my changes

Buildprint can only see changes it makes. If you make changes directly in the Bubble editor on the same branch the agent is working on, it won't be aware of them.

To fix this, ask the agent to resync. This tells it to refresh its view of the app so it can see your manual changes. Without resyncing, the agent may overwrite your work or make decisions based on an outdated view of the app.

Usage limit reached

If you see a usage limit error, this is coming from your AI provider (ChatGPT or Claude), not from Buildprint. Your provider's rate limits apply to all usage across their platform, not just Buildprint.

To resolve this:

  • Upgrade your plan with your AI provider to get higher rate limits.

  • Start a new conversation after upgrading. It may take some time for the new limits to take effect due to caching from the providers.

  • Wait for the rate limit window to reset if you don't want to upgrade.

Was this helpful?