Skip to content
Billing

Credit restoration for failed generations

When Codexe automatically gives back the tokens a project's first generation used, which failures qualify, which don't, and how to see it happened.

Updated

On this page
  1. What qualifies
  2. What doesn't qualify
  3. How much is restored
  4. How you'll know

You should pay for results, not for Codexe's failures. If a project's first generation ends without anything usable because of a problem on Codexe's side, the tokens that generation used are restored automatically. No support ticket needed.

#What qualifies

The first request of a project ended, for good, with:

  • no files at all, even after Codexe's own retry and continuation,
  • a reply cut off so badly that no file could be completed,
  • an AI provider error or refusal before a usable reply,
  • a project on the wrong platform (for example a mod when you asked for a plugin) that Codexe couldn't regenerate correctly,
  • a server error on Codexe's side after you were charged and before anything was saved,
  • an imported project whose first request changed nothing.

#What doesn't qualify

  • A delivered project that contains code errors. You received the files, and Codexe's free repairs and the free Let Codexe try again are there for that. See Auto Repair.
  • A project you changed yourself that then fails to build.
  • Chat messages after the first generation.
  • A result that works but isn't what you wanted: refine it in the chat.

#How much is restored

Exactly what the first generation charged: the upfront estimate plus any settlement, minus anything already returned. It's restored once; running into the same failure again never restores twice.

#How you'll know

  • The project shows "Codexe couldn't complete this project" with the number of tokens restored, your balance, and a Try again button that reopens Create with your original request.
  • The restoration appears in your balance history as a refund.
Credit restoration for failed generations | Codexe Docs