> ## Documentation Index > Fetch the complete documentation index at: https://aidocs.ethanbragdon.icu/llms.txt > Use this file to discover all available pages before exploring further. # FORGE Build States > Reference the FORGE build lifecycle, terminal states, waiting states, and what users or operators should do at each stage. # FORGE build states A FORGE build is a durable job with explicit state. The visible wording can evolve during Alpha, but the lifecycle meaning should remain consistent. | State | Meaning | User action | | ------------ | -------------------------------------------------------------------------------- | ------------------------------------------------------- | | `QUEUED` | Build accepted and waiting for execution capacity. | Wait; investigate only if queue time is abnormal. | | `PLANNING` | FORGE is translating requirements into a project/change plan. | Review plan if interactive approval is exposed. | | `PREPARING` | Workspace, repository snapshot, dependencies, or input files are being prepared. | Usually none. | | `GENERATING` | Files are being created or modified. | Usually none. | | `VALIDATING` | Available validators are running. | Inspect failures if state transitions to repair/failed. | | `REPAIRING` | FORGE is attempting a focused fix after validation failure. | Monitor attempt count and changed files. | | `PACKAGING` | Output is being converted into durable artifacts. | Wait for artifact creation to complete. | | `COMPLETED` | Build finished and required packaging completed. | Review validation and download artifacts. | | `FAILED` | Build could not complete within available constraints. | Read failure stage and logs before retrying. | | `CANCELLED` | Execution was intentionally stopped. | Start a new build if work is still required. | ## Waiting conditions Some implementations can show an intermediate waiting state for capacity, an approval, provider recovery, or another dependency. Waiting is not automatically failure. ## Terminal states `COMPLETED`, `FAILED`, and `CANCELLED` are terminal for that specific build record. Retrying should normally create a new attempt or explicitly supported retry operation rather than mutating history to pretend the original job succeeded. ## Completed does not mean production-ready Completion means the configured FORGE process finished. Review the validation report, artifact contents, and project-specific testing before deploying generated software. ## Failed builds Capture: * build ID * failed stage * validator/tool output * repair attempt count * model/provider errors when surfaced * workspace or artifact status Then fix the actual cause before blindly retrying. Diagnose stuck, failed, or incomplete build jobs.