---
title: Troubleshooting the AI iDecide Builder
description: Most problems happen when the myiDecide Builder tab is hidden or the side panel is closed during a build. Your progress is saved, so the fix is almost always to bring the tab back into view, then open History and…
url: "https://idecide.com/it/knowledge-base/myidecide-builder-2-0/ai-idecide-builder-troubleshooting/"
updated: "2026-10-20"
category: myiDecide Builder 2.0
---

# Troubleshooting the AI iDecide Builder

Most problems happen when the myiDecide Builder tab is hidden or the side panel is closed during a build. Your progress is saved, so the fix is almost always to bring the tab back into view, then open History and click **Resume build**. If you see an error code, find it below.

##

## The myiDecide Builder tab

| Code | What you'll see | What to do |
| --- | --- | --- |
| TAB-01 | Open your presentation in the myiDecide Builder first | Click the tab with your presentation open in the Builder, in the same Chrome window as the side panel. The dashboard and presentation list don't count. Then try again. |
| TAB-02 | Your presentation's tab has to be the one you can see | Chrome pauses tabs you can't see. Click your presentation's tab, wait for the slides to appear, then click Try that again. Your request is still there. |
| TAB-03 | The myiDecide Builder crashed | One crash on a long build is normal, and the step repeats on its own. If the build stopped, wait a minute or two, then open History and click Resume build. |
| TAB-04 | The Builder did not answer, or a slide was skipped | The Builder tab lost focus. Keep it visible for the whole build, don't switch tabs in that window, keep your computer awake, then Resume build. |
| TAB-05 | This presentation is open in another tab | Only one tab can edit a presentation at a time. Close every other tab, window and device that has it open, reload the Builder tab, then Resume build. |

## During a build or an edit

| Code | What you'll see | What to do |
| --- | --- | --- |
| BUILD-01 | A build is running right now | Let the build finish, then send your change again from the finished screen or from History. |
| BUILD-02 | Couldn't read any text out of your file | The file has no readable text, usually a scanned PDF. Save it as a Word document (.docx), .txt or .csv and attach that instead. |
| BUILD-03 | Unknown target | A button points to a slide that isn't in the presentation. Ask for changes and name both ends, like "point the Learn More button on Main Menu to the Pricing slide." |
| BUILD-04 | A note like (NO VOICEOVER) is read out loud | Ask for changes: "make the   slide silent and remove its narration." When editing the script, leave narration empty instead of typing a note. |
| BUILD-05 | Icons or fonts couldn't be found | Nothing is required. If icons or text look wrong, ask for changes, like "set the headline font to \[font name\]." |
| BUILD-06 | File too large, or too many files | Videos must be under 96 MB, and you can attach six files at a time. Compress or trim the file, or send your files in two messages. |
| BUILD-07 | The AI's plan came back garbled | Open History and click Resume build. Your answers and script are kept, and a second try almost always works. |

## The side panel

| Code | What you'll see | What to do |
| --- | --- | --- |
| PANEL-01 | The side panel was closed during a build | Reopen the panel with the AI iDecide Builder icon and choose to continue. If it doesn't offer, open History and click Resume build. Finished slides are saved. |

## Anything else

| Code | What you'll see | What to do |
| --- | --- | --- |
| GEN-01 | Something went wrong | Try once more: Resume build in History, or send your message again. If it happens a second time, send us a build record (below). |

## Getting help

1. Open History and click the **download arrow** next to the presentation to save its build record.
2. Email the file to [Hi@iDecide.com](mailto:hi@idecide.com).
3. Include the error code, your presentation's web address, and what you were doing when it happened.

**Tip:** Give the Builder its own Chrome window while it builds. You can keep working in a different window without pausing the build.