Validation troubleshooting

Why

Either a single section is hung past its 120-second per-call timeout (network glitch with the Claude API mid-stream), or the SSE stream dropped and the client is showing stale state. The orchestrator runs in the background regardless of whether your browser is connected.

Fix

Refresh the report page once. The SSE handler reconnects and shows the real current state of every section. If a section is genuinely stuck, it will time out within ~2 minutes and either retry or fail — the orchestrator handles this without intervention.

Why

Most section failures are JSON parse errors (Claude returned text that didn't match the section's Zod schema) or schema validation misses on a specific field. The credits charged for that section are automatically refunded — you can see the refund in your credit history with the reason tagged to the section key.

Fix

Open the Nova chat from the report and ask “Regenerate thejtbd-analysissection” (replace with the actual section key). Nova runs the section again with the same model — the retry charges the section's normal cost and almost always succeeds on the second attempt.

Why

Sections list their dependencies explicitly. When a dependency fails, every dependent section is marked blocked rather than wasting credits running with incomplete context. For example, if problem-validation fails, ~12 downstream sections block immediately.

Fix

Find the original failed section (it's the one with statusfailed, not blocked) and regenerate that first via Nova. On your next run, the formerly-blocked sections return to pending and execute normally.

Why

Each workspace has a daily ceiling on full validation runs to prevent adversarial credit-harvesting. Free plans cap at 2/24h, Starter at 5, Pro at 15, Team at 30. The limit resets 24 hours after your earliest burst, not on the calendar day.

Fix

Either upgrade the plan, wait for the reset (the error response shows the exact resetAttimestamp), or — if you genuinely need the higher ceiling — contact support with your use case. We'll adjust if the workload is real.

Why

The section's prompt explicitly allows refusal when the model can't find a verifiable source. Empty citation is HONEST output, not a bug — the alternative is fabricated URLs, which we never want. This happens most often on niche / non-English markets where Claude's web search returns thin results.

Fix

Either accept the gap (a missing citation is itself useful information for the founder), or add an explicit research hint via Nova: “Use these sources for demand-signals: [URL1, URL2, URL3]” and regenerate. The model will incorporate them when re-running the section.

Why

The verdict reads every completed section and weighs the signals. When 1-2 sections failed earlier in the pipeline, the verdict synthesises with less context — which biases it slightly toward whatever the surviving sections suggest. Verdict can also feel wrong if your intake answers were thin (e.g. skipped the founder-advantage question).

Fix

First check: were all 30 sections complete? If 2+ failed, regenerate them via Nova and re-run the verdict. Second: open the report's roast section — it usually names the specific assumption the verdict is uncomfortable with. Third: if you have specific context the verdict missed, ask Nova to regenerate the verdict with a hint.

Why

The promote-to-project CTA requires every expected section atstatus === “complete”. If any section isfailed or skipped, the gate stays closed — skipped sections are treated as content gaps that would translate directly to depth gaps in the project blueprint.

Fix

Open the report header. There's a counter showing how many sections are still incomplete. Regenerate them via Nova one at a time. Once everything is complete, the Build button activates.

Why

The orchestrator pauses when the next section would charge below your workspace balance. The idea drops back to intake_completewith the remaining sections at pending.

Fix

Top up from billing, then open the idea and hit Generate again. The pipeline resumes from the first pending section — completed sections are NOT re-charged.