​
Stuck in “Try to Fix”

Building with Lovable is designed to be fast and intuitive, but like any powerful tool, it can sometimes encounter issues. You might find your code doesn’t run as intended, or the AI misinterprets your instructions, leading to unexpected behavior. Here’s a step-by-step guide to help you resolve these problems and get back to building:
1

Use the 'Try to Fix' Button First

When an error appears, your first step should be to click the “Try to Fix” button. Lumi will analyze the logs, identify the problem, and apply a quick fix. If this doesn’t resolve the issue, it’s time to move on to the next step.
2

Diagnose Unexpected Behavior

Sometimes your code runs without errors but doesn’t function as intended. This is known as unexpected behavior and can be tricky to debug. Here’s how to approach it:
  • Review Your Prompt: Double-check your original instructions to ensure they were clear.
  • Isolate the Issue: Examine individual components and logic to pinpoint where things went wrong.
  • Provide Visual Context: Use screenshots or recordings to show the AI exactly what isn’t working.
3

Write More Effective Prompts

Clear and structured prompts produce better outcomes. Follow this format for best results:
  • Project Overview: Briefly describe what you are building.
  • Page Structure: List the key pages and components.
  • Navigation Logic: Explain the intended user flow.
  • Visual Aids: Upload wireframes or mockups.
  • Implementation Steps: Outline the desired build order.
4

Build in a Logical Order

A structured approach to development prevents many common issues. Follow this recommended workflow:
  1. Create the main layout and pages.
  2. Connect your backend or database.
  3. Set up user authentication and roles.
  4. Plan the logic for each feature.
  5. Prompt Lumi to implement features one by one.
5

Use Discuss Mode for Guidance

If you’re feeling stuck, switch to Discuss Mode for assistance:
  • Ask Lumi to analyze the current state of your project.
  • Request a summary of the solutions already attempted.
  • Prompt for new strategies to tackle persistent problems.
6

Apply Advanced Tactics for Tough Bugs

If the issue persists, try these more advanced techniques:
  • Be Specific: Clearly describe the bug and what you expect to happen.
  • Use Visuals: Screenshots or screen recordings are incredibly helpful for illustrating complex problems.
  • Ask for Alternatives: Directly ask, “What else can we try?” to generate new ideas.
  • Roll Back: Restore your project to a previously working version and rebuild the problematic feature step-by-step.

​
Common Troubleshooting Areas

Most issues you’ll encounter will fall into one of the following categories:
  • UI and Layout Glitches
  • API or Backend Errors
  • Prompt Misinterpretations
  • AI Unresponsiveness or Malfunctions
  • Platform or Integration Failures
Expand the sections below to identify specific symptoms and find actionable solutions for each.

​
General issue

Switch to Chat Mode and ask: “Something isn’t working correctly. Can you explain the problem and tell me what you’ve already tried?”
  • Inspect the component hierarchy and review the applied styles.
  • Use screenshots to clearly illustrate any visual glitches.
  • Prompt Lumi directly: “This element is misaligned. Please fix it.”
  • Try this prompt: “Let’s take a step back. Analyze the error and propose an alternative solution.”
  • Break the task down into smaller, more manageable steps.
  • If errors persist, use the revert button to roll back to a working version.
This indicates a platform problem and should not happen. Please report it immediately to our support team.
First, try a hard browser refresh. If the issue is not resolved, please contact support for assistance.

​
AI Reliability

  • Write clear, well-structured prompts.
  • Employ reverse meta prompting techniques.
  • Test prompts in Discuss Mode before implementing major changes.
This is an unexpected issue. Please report it to our support team for immediate assistance.
Refine your prompt to clarify your objective, or request a step-by-step debugging guide from the AI.
Implement changes incrementally. If problems continue, revert to a stable version or use Discuss Mode for debugging.
If you encounter error loops or flawed logic, revert to a stable version. Then, provide more specific context in your next prompt, using the visual editor or by attaching a knowledge file.
The AI may be misinterpreting your request or targeting the wrong files. Provide highly specific instructions, or make the edits manually.
This is an unexpected issue. Please report it to our support team for immediate assistance.
  • Avoid retrying the exact same prompt; instead, simplify or rephrase it.
  • Ask the AI: “What solutions have we already attempted?”
  • Restore a previous working version of your project.