Skip to main content

How to get help when a build stalls or fails

E
Written by Errin Veney

Before you begin

  • Keep the current project intact. Do not delete, repeatedly rebuild, or re-import until the failure is understood.

  • Capture what you expected, what happened, and the last instruction that ran.

Recover the current project

It looks like your project did not reach the result you expected.

Please do not keep repeating the same instruction and spending credits. Give us the smallest possible

description of the problem:

Expected

  • [What you wanted to happen]

Actual

  • [What happened instead]

Last instruction

  • the last instruction

You can reply directly to this email or open support from the project. A person can review the exact

point where the build stopped.

If the project is based on an existing codebase, do not delete or re-import it yet. We may be able to

correct the current version without making you start again.

Our goal is to get you back to a working preview, not send you through a troubleshooting maze.

Common mistakes

  • Repeating the same failed prompt and consuming more credits.

  • Deleting the project before support can inspect it.

  • Sending a screenshot without explaining expected versus actual behavior.

Frequently asked questions

Will I lose my project if a build fails?

A failed or stalled action does not mean the project is lost. Keep the project intact and provide the project context so the current version can be inspected.

What should I send to support?

Send the expected result, the actual result, the last instruction, and a screenshot when it helps. Do not include secrets or unnecessary sensitive data.

Did this answer your question?