Troubleshooting

Generation failed

Your edit or generation failed. What to try next.

Occasionally a site generation or edit doesn’t complete. The chat shows a Generation failed banner and offers a Retry button. Here’s how to recover.

Try Retry first

In most cases, retrying works. The AI gets a fresh attempt with the same message, and common transient issues (timeouts, hiccups) resolve.

  • Click Retry in the chat.
  • Wait for the generation to complete.
  • If it succeeds, you’re done.

Failed generations that consumed credits are automatically refunded when the refund policy applies — so Retry is usually a safe first move.

If Retry fails

Try a different angle. One of these usually helps:

Simplify the prompt

If the original prompt tried to do several things at once, break it up:

  • Undo the failed state (if any partial version was produced).
  • Send a smaller, more focused Edit.

See Iterate in small steps.

Switch to Discuss to diagnose

Switch to Discuss and ask PageFork what went wrong:

“The last edit failed — why might that be?”

Discuss can often explain: the request was ambiguous, an element didn’t exist, or a pattern was ambiguous.

Note: once you send a Discuss message after a failed generation, the Retry button disappears. You can still re-send the original Edit manually.

Rewrite the prompt

After understanding the issue, send a cleaner Edit prompt with more specifics — see Writing great prompts.

Common causes

  • Too much scope in one prompt. Fix: smaller prompts.
  • Ambiguous references (e.g. “change the button” on a page with many buttons). Fix: use Select mode to reference the specific element.
  • Conflicting instructions (e.g. “keep this exactly” + “make it completely different”). Fix: pick one.
  • Network blip. Fix: Retry.

When to contact support

If the same prompt fails three times in a row and you can’t tell why, send support:

  • The site URL.
  • The approximate time of the failure.
  • The prompt you were trying.

Next