> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aiblueprint.web.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Generation troubleshooting

> Recover a slow, interrupted, or stopped Blueprint safely.

## Generation is still running

Blueprint generation continues on the server. You can close the tab and reopen the project from **My Blueprints**. Active document cards show a spinner, and **Project Health** shows **Generating** until the current run finishes.

<Steps>
  <Step title="Reopen the same project">
    Open **My Blueprints** and select the existing card. Do not create a duplicate.
  </Step>

  <Step title="Refresh once">
    Allow the page to reload the stored run status. Repeated rapid refreshes do not make generation faster.
  </Step>

  <Step title="Check the status">
    If document cards still show spinners and **Project Health** shows **Generating**, leave the run active. If it is paused, follow the recovery card.
  </Step>
</Steps>

You cannot select **Sign Approve Blueprint** or export **Project ZIP** while generation is active. After generation finishes, open all 10 current document cards, including any **Not Required** stub, until each shows **Reviewed**.

## The process is paused

<Frame caption="Sanitized recovery example. The real Support ID is unique to your incident.">
  <img src="https://mintcdn.com/ia-blueprint/xvYlFUH0B2wc9dt4/images/recovery-support.svg?fit=max&auto=format&n=xvYlFUH0B2wc9dt4&q=85&s=a7495c6c196b343e20a6492bb490e56f" alt="Paused Blueprint process with Retry, Support, and My Blueprints actions" width="1200" height="560" data-path="images/recovery-support.svg" />
</Frame>

Completed stages remain saved. The recovery card may offer one **Retry**. Select it once and keep the page open long enough to observe the state change. If Retry is unavailable or the process stops again, create a Support ticket with the Support ID.

### When a Support ID appears

A Support ID is created when the server records a Blueprint generation incident that has stopped the project, not merely because a healthy run is taking longer than expected. The same incident keeps the same Support ID across page refreshes. It links the visible recovery card to the project, failed stage, retry history, and resolution status that the Support team can inspect safely.

The Support ID is not a ticket number. Selecting **Open Support** carries the project and Support ID into the ticket form; after submission, the ticket receives its own number for the email conversation. Keep both references when Support asks for them.

<Note>
  If the status still says that generation is active, wait or reopen the same project. Do not create a Support ticket only because a normal background stage has not finished yet.
</Note>

## Common conditions

<AccordionGroup>
  <Accordion title="Insufficient credits">
    Open **Billing** and compare the required action with the regular and add-on balances. Top up if needed, then return to the same project.
  </Accordion>

  <Accordion title="A document says Needs Repair">
    Open that document and regenerate it before global approval. Review the new current version after regeneration. This is a document-quality state, not necessarily a failed whole-project run.
  </Accordion>

  <Accordion title="A document load error persists">
    Use the page Retry once. If it still fails, link the Blueprint in Support and name the document and current version.
  </Accordion>

  <Accordion title="A resume is offered after interruption">
    Resume continues missing work. It does not restart completed stages, and a valid paid interrupted run can resume without another generation charge.
  </Accordion>
</AccordionGroup>

<Warning>
  Do not repeatedly press Retry, create duplicate projects, or submit the same paid action in multiple tabs. These actions make incident diagnosis and payment reconciliation harder.
</Warning>