Troubleshooting

When a build stops, a preview does not start, or an application does not look or behave as expected, use this guide to identify what happened and choose the best recovery action.

---

Quick action guide

When an issue occurs, DeplAI provides distinct actions:

---

Build failed

A Build failed status means DeplAI encountered a problem while creating the application before it could start a working preview.

Common causes

• Conflicting or ambiguous requirements: The product request contained contradictory features (for example, requiring anonymous guest checkout while simultaneously mandating strict verified user accounts for all actions).
• Overly broad initial scope: The initial prompt requested too many complex systems at once, exceeding a single generation boundary.
• Temporary generation interruption: A service interruption occurred during code creation.

Recommended actions

1. 1Check Logs: Open the Logs panel to see the last recorded activity (such as *Understanding application* or *Building application*).
2. 2Use Retry: If the request is clear and you want a fresh build attempt, click Retry.
3. 3Refine your request: If the request was very long or broad, narrow the initial request to the core product workflows and use Modify later to add secondary features.

---

Preview unavailable

A Preview unavailable or Preview could not start status means that although code was created, the preview runtime could not start or maintain the running application.

Common causes

• Startup issue: The generated application encountered a missing dependency or configuration issue when launching.
• Temporary runtime stop: The temporary preview environment stopped after a period of inactivity or a workspace refresh.
• Version mismatch: The inspector is displaying a historical version whose temporary runtime is not actively running.

Recommended actions

1. 1Check the version under review: Previews run for the active build. If you selected an older saved version in Files, the preview runtime for that older version may be stopped.
2. 2Use Ask DeplAI to fix: If the preview failed during the latest build, click Ask DeplAI to fix (or select Fix in the composer). DeplAI will inspect the startup diagnostics and repair the application.
3. 3Inspect saved source: Even when a temporary preview is unavailable, your code is never lost. Open Files to browse the saved source code or use Download code to retrieve it.

---

Application needs attention

A build ends in Needs attention when DeplAI started the application, but one or more required product checks did not pass, and automated improvements were unable to resolve the issue within the current build cycle.

Common causes

• A required workflow did not pass: An essential journey (such as signing in, adding an item to a cart, or submitting a booking) did not behave correctly during evaluation.
• Material visual or layout issues: Key screens showed severe display problems, broken elements, or unreadable navigation on desktop or mobile views.
• Required feature missing: An explicit requirement from your prompt was not detected during verification.

Recommended actions

1. 1Open Checks: Switch to the Checks panel to see which validation step failed (for example, *Workflow check: patient booking* or *Desktop and mobile presentation*).
2. 2Review the running preview: If Preview available is still active, test the failing screen yourself to see the current behavior.
3. 3Use Ask DeplAI to fix: Click Ask DeplAI to fix to direct DeplAI to resolve the specific check failure.
4. 4Use Modify with specific guidance: If DeplAI struggled with a specific screen layout, send a targeted modification describing the desired appearance.

---

A requested feature is missing

If DeplAI completed the build and marked it Ready, but you notice a feature from your original description is missing or incomplete:

Common causes

• The original prompt focused heavily on other aspects of the application, and the missing feature was not given sufficient detail.
• The feature requires specific demonstration data or role access to be visible in the preview.

Recommended actions

1. 1Check demonstration roles and navigation: Verify whether the feature is located under an administrator area or requires signing in as a specific role.
2. 2Use Modify: Send a targeted change request in the conversation.

*Example:* > "Add a customer review and rating section below the product details on the product page."

1. 1Attach relevant files: On the Files panel, locate the page component and attach it to your change request for extra precision.

---

Modification did not produce expected result

When you submit a change request using Modify, but the updated version does not reflect what you intended:

Common causes

• Vague request phrasing: Requests like "make it look nicer" or "fix the dashboard" leave too much room for interpretation.
• Multiple competing changes: Requesting ten distinct visual and functional changes in a single prompt makes verification difficult.

Recommended actions

1. 1Revert to previous version: Your previous saved version is safely preserved in history. Select the previous Ready build to view or download that version.
2. 2Send an explicit, focused change: Describe the exact change you want, specifying the page, element, and expected behavior.

*Example:* > "On the checkout page, make the order summary sticky on the right side and show a line item for estimated tax."

1. 1Submit incremental changes: For major redesigns, request one screen or workflow modification at a time.

---

Diagnostic support

If an issue persists after trying Retry and Fix:

• Note the Build number and Application version shown in the conversation inspector.
• Review the Checks summary and the last entry in Logs.
• Contact support at support@deplai.tech with your conversation link and the recorded activity summary.

Related: Checks | Activity | Ask DeplAI to fix | Retry a build | FAQ