Leafage Help
Download

Generation failed or got stuck

Fix failed, stopped, slow, or missing Leafage generations.

Last updated June 26, 2026

Generation depends on three things working together: your Leafage license or trial, the local Codex CLI, and the project folder where results are saved.

First checks

Try these in order:

  1. Open Settings -> Codex and confirm the Codex CLI is ready.
  2. Confirm your trial still has image generations left, or that your lifetime license is active.
  3. Make sure the project folder is still available.
  4. Quit Leafage with Command + Q, reopen it, and try a small x1 generation.

If Codex is missing

If a generation fails immediately with a Codex error, follow Codex isn’t detected.

Common signs:

  • Settings does not show Codex as ready.
  • codex --version fails in Terminal.
  • Leafage has a custom Codex path that no longer exists.

If your trial is out of images

When the 50 trial image generations are used, Leafage keeps editing and export available but blocks new generation.

Open the upgrade dialog from the banner or from license settings to activate lifetime access.

If Codex is out of credits

Leafage uses your own Codex subscription. If Codex reports exhausted credits or quota, Leafage cannot generate until your Codex account can generate again.

Check Codex directly in Terminal or the account you use for Codex.

If a generation is slow

Generation time depends on Codex, prompt complexity, reasoning effort, image count, and the number of active runs.

To reduce wait time:

  • Try x1 before x4.
  • Use Medium or Low reasoning effort for rough exploration.
  • Stop runs you no longer need.
  • Avoid running many large branches at once.

If the result never appears

Leafage watches Codex and then copies the generated asset into your project. If the app quits, the computer sleeps, or the project folder disappears during a run, the result may fail to attach.

Try:

  1. Reopen the project.
  2. Check whether the node has a failed or stopped generation state.
  3. Run the node again.
  4. If it repeats, export a project backup and contact support with the error message.

What to send support

Include:

  • macOS version.
  • Leafage version.
  • Whether you are on trial or lifetime access.
  • The exact error shown in Leafage.
  • Output of codex --version.
  • Whether the same prompt works in a fresh project.