Error Recovery
How a build recovers from its own mistakes — and why a build that fails is never charged.
Audit, then repair
In Economy and Power, an audit scores the result and returns the fix for each problem it finds. When it finds something worth fixing, a repair pass applies those fixes. Weak copy gets a rewrite and a second check. Builds that are play-tested or browser-tested — 3D games, animations, instant web apps — are repaired, tested again, and the repair is kept only if it is better than what it replaced.
Corrected, not rejected
Small faults are fixed in place rather than failing the build: over-long text is trimmed, bad links become #. See Validation.
Optional stages fail quietly
If an optional stage cannot run — the intake questions, the visual review — the build carries on without it and says which stage failed and why. An optional stage never takes the build down with it.
When the build itself fails
If the build cannot finish — too many builds at once, the service is busy, a request took too long — you get a plain message and you are not charged. Most of these are worth trying again. Each one is listed in Build Failed.