Skip to content
Genesis Help

Fixing errors

Sometimes a change breaks the preview — a red error screen instead of your page. Genesis has a dedicated repair path for exactly this.

How to trigger it

Section titled “How to trigger it”
  • Click Fix this error on the error display, or
  • Type “fix this” / paste the error text into chat.

What it does differently

Section titled “What it does differently”

This isn’t a normal edit pass. The repair path:

  • Reads the real error — message, the file it points to, related imports — instead of guessing from your description.
  • Skips the planning phase — error fixes are precise, line-level work, so it goes straight in.
  • Prefers the smallest possible change that makes the error go away (a missing import, an unclosed tag, a missing package), rewriting more only when a file is genuinely corrupted.
  • Reloads the preview fresh afterward, so you’re not looking at a stale error.

Typical fixes land in 10–20 seconds.

If the error persists

Section titled “If the error persists”

Click Fix this error again — the second pass diagnoses from the new state. If a change just made things worse overall, undo is often the faster reset, then re-ask for the change differently.

Section titled “Related”

A failed publish (rather than a broken preview) has its own repair path — see Fixing publish failures.