Castaly is waiting for a clarification, choice, or missing detail before it can continue.
Resolve Blockers
A Project can pause when Castaly needs your input, finds a Spec conflict, hits an execution failure, loses an expired Preview, or needs runtime configuration before Publish.
These states are recoverable. In most cases, you do not restart the Project. Read the state, follow the matching action, and continue from the current context.
Find the state first
Section titled “Find the state first”Start with the label shown on the Project card, workspace header, Graph summary, or Preview tab.
| If you see | What it means | Next step |
|---|---|---|
| Needs your input | Castaly is waiting for your answer or decision. | Open Chat and reply. |
| Setup failed | Castaly could not finish creating the initial Project. | Retry setup when available, or review the failure in Chat. |
| Build blocked | The Spec has a conflict that must be resolved before Build can continue. | Resolve it in Chat, then run Build again. |
| Build failed / Tests failed | Implementation or automated checks failed. | Use the recovery action shown in the workspace. |
| Preview failed | Castaly could not prepare or restore the Preview. | Retry the Preview action or follow the workspace recovery. |
| Preview expired | The Preview link expired, but the build result can be restored. | Use Resume. |
| Configuration required | A required runtime secret is missing. | Add it in Project Settings. |
| Publish failed | Castaly could not finish publishing the Project Version. | Retry Publish after reviewing the failure. |
Needs your input
Section titled “Needs your input”The question or request appears in Chat, where you can answer naturally.
Once you respond, Castaly uses your answer to continue the current work.
Open Chat, read what Castaly needs, and reply. You do not need to create a new Project or start a new conversation.
Setup failed
Section titled “Setup failed”Setup failed means Castaly could not finish the initial Project setup. This happens before the normal Spec → Build → Preview loop begins, so it is not the same as Build failed.
Possible causes include insufficient Credits, a temporarily unavailable AI provider, or an invalid first-pass Project structure.
If the workspace shows a retry action, use it. If setup keeps failing, describe what you were trying to create in Chat so Castaly has the context for recovery.
Build blocked — a Spec conflict
Section titled “Build blocked — a Spec conflict”When you press Build, Castaly checks the Spec for contradictions before writing any code — for example, one section requires Google login while another says this version only supports email. If it finds conflicts, the Project enters Build blocked and nothing gets built, so nothing half-finished is left behind.
Read the conflicts in Chat
Castaly lists each conflict in a card in Chat, with a short explanation, suggested resolutions, and source references.
Choose how to resolve each one
Pick one of Castaly’s suggested options, or write your own answer. Resolve every conflict in the card.
Apply, then Build again
Castaly updates the Spec and Graph from your choices. Press Build again to re-run the check — it doesn’t rebuild automatically.
Start a Build explains why this check runs before code, not after.
For the detailed Conflict Card flow, see Resolve Spec Conflicts.
Build, test, preview, or publish failed
Section titled “Build, test, preview, or publish failed”Failure states mean Castaly started work, but one step could not finish. The failed step determines the recovery action.
| State | What failed | Recovery |
|---|---|---|
| Build failed | Implementation failed before the Project reached a usable Preview. | Use Retry or Continue Build when shown. |
| Tests failed | Automated checks failed during Build. | Use the recovery action shown in the workspace. Castaly can usually continue from the failed point. |
| Preview failed | Castaly could not prepare or restore the running Preview. | Retry the Preview action or follow the workspace recovery. |
| Publish failed | Castaly could not finish publishing the Project Version. | Retry Publish after reviewing the failure message. |
You do not restart the whole Project. Recovery actions appear after the running work stops; while work is still active, the buttons stay hidden or disabled.
Preview expired
Section titled “Preview expired”Preview expired is not a failure and it does not mean the Project lost its build result. It means the running Preview link timed out.
Use Resume to restore the Preview. Resume brings back the Preview for the existing build result; it does not start a new Build.
Configuration required — a missing secret
Section titled “Configuration required — a missing secret”Some features need a runtime secret or API key — a payment key, a third-party token. A missing one does not block Building or Preview. The preview still deploys and you can walk it; the affected features just may not work, and the Project shows Configuration required.
What it does block is Publish. To clear it:
Open Project Settings
Use Set up from the Configuration required state, which opens Project Settings at the runtime secrets section.
Add the missing secret
Enter the required key. Saved secrets are stored securely and shown masked afterward.
Publish
With the secret in place, the publish block clears.
See Runtime Secrets for managing keys.
Retry vs Continue Build
Section titled “Retry vs Continue Build”When a Build stops, the workspace may show one or more recovery actions.
Runs the failed action again from the point where it broke.
Continues from the last completed point when Castaly has recoverable work ready to execute.
Restores an expired Preview. It is not a rebuild.
Use the action shown in the workspace. Castaly only shows recovery actions that make sense for the current state.
Next: Runtime Secrets explains how to add missing keys.