Skip to content

Getting started

Div-idy build progress, saved drafts, and recovery

Div-idy documentation Updated

A Div-idy build generates or edits React and TypeScript source, checks and compiles the code, and saves the finished result as a private draft. Wait for the saved result before judging the new app. Progress messages or intermediate images are not confirmation that a completed project has been saved or published.

What happens during a build?

The normal build moves through preparation, generation, code checking, and saving. TypeScript checks help catch invalid types and unsupported imports; compilation produces the browser code used by the preview. Div-idy saves the checked source and compiled result together.

Code checks are not a full browser test. Use the finished preview to verify navigation, calculations, forms, and mobile controls. A build can compile successfully while still needing a behavior or design adjustment.

Can you leave the page while it builds?

Supported background builds continue on the server after you leave the browser page. When you return, Div-idy checks the existing build’s status and can open its saved result. Closing a tab does not necessarily mean the build failed.

This depends on the active server process continuing to run. Background status recovery is not a guarantee that unfinished generation survives a server restart or service interruption. Do not submit a duplicate prompt just because the original tab closed.

What do the recovery messages mean?

  • Still building: work is active; wait for the saved result.
  • Finished project is saved: open the saved project and review it.
  • Reconnecting: status is temporarily unavailable; checking status does not start another build.
  • Unconfirmed: completion cannot be established; inspect the last saved draft before deciding what to do next.
  • Failed: the build did not finish; the last saved project remains available.

How should you recover from an error?

  1. Restore your connection and reopen the project.
  2. Read the build status and open any confirmed saved result.
  3. Check whether the requested change is already present.
  4. After a confirmed failure, simplify or correct the request before trying again.

If the status remains unclear, keep the error text and project details for support. Repeated generation requests can create unnecessary work and usage.

Does recovery change the live app?

Recovering a saved build opens its draft. It does not publish it. Existing live pages remain separate from new draft edits until you publish an update. If a build shows visual progress, treat it as a progress aid; the final saved preview is the place to test the app.