# Troubleshooting Your App

> Building with AI is like having a conversation with a good friend who wants to help but sometimes needs clarification. So, don't worry if your first ...

- Source: https://www.taskade.com/learn/genesis/troubleshooting
- Section: Taskade Genesis
- Updated: 2026-11-14
- Index of all pages: https://www.taskade.com/learn/llms.txt

![](https://www.taskade.com/static_images/learn/genesis/troubleshooting-574c843a.jpg)

## Overview

> **TL;DR:** Start with the exact screen, action, and expected result. Taskade Genesis recovers interrupted builds and keeps failed turns visible after reload. Use **Try again** for temporary failures, **Fix with AI** for app errors, and [Version history](https://www.taskade.com/learn/genesis/version-history) when repeated repair attempts do not clear the issue.

![](https://www.taskade.com/static_images/troubleshooting-your-app-v2.gif)

AI works like a conversation with a good friend. The friend wants to help, but sometimes needs clarification. Your first result does not have to be perfect. Treat troubleshooting as a way to teach Taskade Genesis about your business.

---

### Why Things Go Sideways

Taskade Genesis can miss the mark for one main reason. People are not always precise about what they want.

**Common culprits:**

- ❌ We assume Taskade Genesis knows our industry context.
- ❌ We focus on features instead of explaining the actual problem.
- ❌ We forget to mention who will use the app and how.
- ❌ When we need to be specific, we use vague language instead.

Once you know what to look for, each of these issues has a clear fix.

---

### Get Back on Track

This is the classic "I asked for a booking system and got... something else entirely" situation. It usually means Taskade Genesis needed more context.

**Here is how to fix it:**

Explain the real-world problem you want to solve.

Instead of "I need a booking system," write something like:

```
"I run a massage therapy practice where clients need to book 60 or 90-minute sessions with specific therapists. Clients should see available time slots, pay a deposit through Stripe, and get confirmation emails. We also need to block out lunch breaks and handle last-minute cancellations."
```

![](https://www.taskade.com/static_images/learn/genesis/troubleshooting-aa717e8e.jpg)

See the difference? The second prompt gives Taskade Genesis real business context.

> **💡 Note:** Explain your business as if the reader never worked in your industry. That level of detail gives the AI all the [context](https://www.taskade.com/learn/genesis/app-context) it needs.

---

### Add Missing Features

Sometimes Taskade Genesis builds exactly what you asked for, and then you realize you forgot something. You focused on the main feature and missed the supporting processes.

**Here is how to fix it:**

Walk through the complete user journey from start to finish. What happens before someone uses your main feature? What happens afterward?

For example, if you built a contact form but forgot about file uploads:

```
"The contact form looks great, but I also need clients to upload project briefs and reference materials when they submit requests. Add a secure file upload section that accepts PDFs and images."
```

Taskade saves what a client picks in that field with their submission, so a later automation step can read it. Taskade reads the words off a scanned page or a phone photo, on files up to 10 MB, the limit for a file sent through a published app. See [File Uploads in Your App](https://www.taskade.com/learn/genesis/app-uploads) for where the file lands. See [Read Scanned Documents](https://www.taskade.com/learn/genesis/scanned-documents) for what it reads.

> 💡 **Note**: Taskade Genesis shows pills with recommended edits after each iteration.

![](https://www.taskade.com/static_images/learn/genesis/troubleshooting-7e51b440.jpg)

---

### Build On Brand

Generic-looking apps do not inspire trust or excitement. If your app can belong to any business, add some personality.

**Here is how to fix it:**

Describe your business personality in simple terms:

- "We are a yoga studio, so make it feel calm and zen: soft colors like sage green and cream, rounded corners, and peaceful vibes"
- "We are a fitness gym, so make it energetic: bold colors like orange and black, strong typography, and buttons that motivate action"
- "We are a law firm, so keep it professional but approachable: navy blue and gray colors, clean lines, and trustworthy messaging"

> 💡 **Note**: "Make it look professional" is not enough. Tell Taskade Genesis what professional means for your business and audience.

---

### Connect Integrations

Integration problems usually start with unclear instructions about data flow. Taskade Genesis must know exactly what information goes where, and when.

**Here is how to fix it:**

Instead of limiting instructions to:

```
"Connect this to Slack"
```

Write prompts that are specific and logical:

```
"When someone submits the contact form, send a message to our #leads Slack channel with the person's name, email, and which service they're interested in. Include a link to their full submission."
```

> **💡 Note**: Test with real workspaces and email addresses, not dummy accounts. Real accounts show sign-in and permission problems early.

---

### Speed Things Up

Speed problems usually come from too much work at once: heavy images, too many items on screen, or complex processes.

Visual performance problems to watch for:

- Large images that take a long time to load.
- Too many items on one screen.
- Heavy animations or effects that make scrolling choppy.
- Complex layouts with lots of elements competing for attention.

**Here is how to fix it:**

- "Make this load faster by showing the booking calendar first, then loading the service descriptions and pricing in the background. Most people want to see available times right away."
- "The homepage is loading too slowly because of all those high-resolution photos. Compress the images and only show 3-4 key services upfront, with a 'See More' button for the rest."
- "Simplify the dashboard by showing only the essential metrics first: revenue, bookings, and alerts. Move the detailed charts and reports to a separate tab so the main view loads instantly."

> **Tip:** Ask Taskade Genesis to make one measurable improvement at a time. For example, ask it to reduce the first screen's image size before changing the whole dashboard.

---

### Start Fresh

Sometimes a rebuild is faster than more patching. Start over when:

- You made multiple major change requests and it still does not feel right.
- You learned something fundamental about your users that changes everything.
- The app became too complex during multiple fix attempts.
- You realized you need a completely different type of solution.

**Here is how to fix it:**

1. Write down everything you learned from the first attempt.
2. Create a much more detailed prompt from those insights.
3. Include specific examples of what must happen and what must not happen.
4. Reference other apps: "Like the booking flow on [website], but simpler"

A restart is not a failure. You use what you learned to build something better.

---

### Recover an Interrupted Build

Let Taskade Genesis finish its recovery step before you send a second request. Releases v6.227.0 through v6.231.0 improved several failure paths:

- Failed Taskade EVE turns stay visible after reload with a stable Error ID.
- Temporary build service failures recover more reliably.
- An interrupted first build can return to a useful build state.
- Database timeouts can tell the app to retry, instead of showing an unknown failure.
- A stalled first build can continue without a misleading resume prompt.

These changes reduce dead ends, but they do not make every build infallible. If the same error returns, do not send the same prompt again. Open details, copy the Error ID, and use the matching recovery path that follows.

---

## Common Issues and Errors

Do you run into errors while you build? Here is a list of common errors, why they happen, and how to resolve them.

### Start With the Decision Tree

Find the symptom, then follow the arrow to the first thing to check. Most issues clear at the first stop.

```text
┌──────────────────────────────────────────────────────────────────┐
│  What's wrong?                 →  Check this first               │
├──────────────────────────────────────────────────────────────────┤
│  App won't load / blank screen →  Check publish status           │
│  App opens but shows no data   →  Connect the app to its         │
│                                   Project                        │
│  A button does nothing         →  Re-run the action              │
│  App feels slow                →  Trim images and items          │
│  Publish is blocked            →  Remove a stray key             │
│  AI is off-tone or off-topic   →  Re-state the rule              │
└──────────────────────────────────────────────────────────────────┘
```

### Match Symptom to Fix

Scan this table for what you see on screen, then jump to the matching section or guide.

| Symptom | Likely cause | Fix |
| --- | --- | --- |
| App opens but the lists, cards, or numbers are empty | The app is not connected to its Project, so it has nowhere to read or save data | Open the app, pick the Project that holds your records, and re-publish. See [App Context](https://www.taskade.com/learn/genesis/app-context). |
| A page or an automation reads an empty field, or a public agent does not know what it needs to know | A link between the app, a project, an automation, or an agent is broken | Ask [Taskade EVE](https://www.taskade.com/learn/agents/eve-assistant) to check every link and list each broken one with its fix. See [View Your Workspace DNA Graph](https://www.taskade.com/learn/genesis/dna-graph#spot-problems-in-a-workspace). |
| A list shows nothing or does not save, and the **Publish** menu says that lists are locked | The app has no sign-in screen, and the list needs a signed-in person to show or save | Click **Add sign-in with EVE** in the note to ask Taskade EVE for sign-in. See [Locked lists in an app with no sign-in screen](https://www.taskade.com/learn/genesis/publishing#locked-lists-in-an-app-with-no-sign-in-screen). |
| In a cloned App Kit, a form or a button that runs an automation does nothing | A copy leaves each automation with a webhook trigger or an agent tool trigger off, and the form or the button starts one of those | Open the automation in your copy and turn it on. See [Clone into Your Workspace](https://www.taskade.com/learn/genesis/community-kits#clone-into-your-workspace). |
| A button or form does nothing when clicked | The action behind it stalled or never finished | Re-run the action. If it keeps failing, click **Fix with AI** or describe the step to [Taskade EVE](https://www.taskade.com/learn/agents/eve-assistant). |
| App takes a long time to load | Heavy images or too many items on one screen | Show fewer items up front and compress images. See [Speed Things Up](#speed-things-up). |
| Publish is blocked or warns about a key | A stray secret key is sitting in your app | Move it into [App Secrets](https://www.taskade.com/learn/genesis/app-secrets), then publish again. |
| Screen stuck on "Spinning up" or blank | A file or library reference broke after an edit | Click **Fix with AI**, or roll back with [Version History](https://www.taskade.com/learn/genesis/version-history). |
| AI answers off-topic or off-brand | The rule or context was not clear | Re-state the rule in plain words. See [App Context](https://www.taskade.com/learn/genesis/app-context). |
| A document came back with no text | Reading happens in the **Turn a file into text** step, and GIF and BMP sit outside what it reads | Point that step at the file field and run the automation. It reads scanned PDFs plus PNG, JPG, WebP, and HEIC photos, up to 20 MB. A file sent through a published app stops at 10 MB. See [Read Scanned Documents](https://www.taskade.com/learn/genesis/scanned-documents). |
| Cards or rows show a placeholder name instead of the record's real one | The card title does not point at the record's own name field | Ask Taskade Genesis to rebuild that view. Apps built or rebuilt from here show each record's real name on its card or row. |

### Your App Shows No Data

This is the most common surprise. Your app looks finished, but every list, card, or number sits empty.

In Taskade Genesis, your app and your data live in two places. The app is the screen people see. The Project is the table of records behind it: your customers, jobs, invoices, or whatever you track. The app reads from and writes to its Project. If the app does not point at the right Project, it has nowhere to get data, so it shows nothing.

**✅ How to fix it:**

Open your app. Pick the Project that holds its records, then connect them. Re-publish the app. Once the app and Project are linked, your records appear, and new entries save back to the same place. See [App Context](https://www.taskade.com/learn/genesis/app-context) for a full walkthrough.

---

### Context Limit

If the error card says the request is too long, split the edit into smaller parts.

1. Start a new chat.
2. Name one page or feature.
3. Ask for one clear change.
4. Test it before asking for the next change.

---

### Temporary Service Error

When the card says Taskade is taking longer than expected or temporarily unavailable, wait briefly. Click **Try again** once. If the error repeats, copy the Error ID and contact support.

---

### Usage or Account Message

When the issue involves usage, account activation, billing status, or plan access, follow the action on the card. A wait does not resolve an account requirement.

---

### A Button That Runs an Automation Says Wait

A button or form in your app can start an automation. Two messages mean that the automation is fine and only needs time:

| What you see | Cause | Fix |
| --- | --- | --- |
| A test submission in Taskade shows **Still saving** and "is still running. Check its runs." | The automation takes longer than the app waits for an answer | Do not submit again. A second submit runs the automation a second time. Click **See run** or open the **Runs** tab to watch it finish. |
| A visitor sees "Too many requests from your network. Wait a minute, then try again." or "Too many requests from your network today. Try again tomorrow." | Each network can start each automation of the app only a limited number of times in a minute and in a day. A form has a limit for each minute only, so one visitor cannot block the form for all other visitors | Ask the visitor to wait a minute, or to try again the next day. The limit protects your credits and your automation runs from repeated guesses. |

If the run in the **Runs** tab failed, open the run and fix the step. Then run the automation again. See [How Automations Work](https://www.taskade.com/learn/automation/automations-execution).

---

### A Blank Screen

When the preview stays blank or shows "Spinning up" longer than expected, open error details.

![](https://www.taskade.com/static_images/learn/genesis/troubleshooting-f1ed1f33.jpg)

1. Click **Show error details**.
2. Click **Try again** for a temporary loading failure.
3. Click **Fix with AI** for an app error.
4. Test the preview after Taskade Genesis finishes.
5. If the same error remains, restore a working revision.

---

## Use Version History

If your app breaks after changes, you can restore a previous working version.

---

### Choose When to Restore

- Your app stopped working after recent changes

- You made multiple changes and are not sure what broke it

- You want to undo recent modifications quickly

- The app still shows errors after fix attempts

### Restore an App Revision

1. Open your Taskade Genesis app and go to Preview.
2. Open **Version history** from the toolbar.
3. Find the **Live** badge so you know what visitors currently see.
4. Preview the revision you want to restore.
5. Click **Restore Version** and test the app.

![](https://www.taskade.com/static_images/learn/genesis/troubleshooting-49310d47.jpg)

![](https://www.taskade.com/static_images/learn/genesis/troubleshooting-5803b44d.jpg)

---

### Diagnosis Decision Tree

When something is off, trace the symptom to the DNA pillar that misbehaves:

```mermaid
flowchart TD
    S[Symptom<br/>something's wrong]:::s --> Q1{What's<br/>broken?}:::q
    Q1 -->|Data is missing<br/>or wrong| M[Memory issue]:::m
    Q1 -->|App does the<br/>wrong thing| I[Intelligence issue]:::i
    Q1 -->|Action doesn't<br/>fire| E[Execution issue]:::e
    Q1 -->|Visual only| UI[UI issue]:::ui

    M --> MFIX["• Add context files<br/>• Check project schema<br/>• Re-prompt with data examples"]:::fix
    I --> IFIX["• Try a different model<br/>• Refine agent instructions<br/>• Re-prompt with user flow"]:::fix
    E --> EFIX["• Check automation trigger<br/>• Inspect filter conditions<br/>• Verify integration auth"]:::fix
    UI --> UIFIX["• Describe change to Taskade EVE<br/>• Use Element Selector<br/>• Pick a different style"]:::fix

    classDef s fill:#1a0d0d,color:#ef9a9a,stroke:#b71c1c,stroke-width:1.5px
    classDef q fill:#1e1e2e,color:#cdd6f4,stroke:#475569,stroke-width:1.5px
    classDef m fill:#0d1b2a,color:#7dd3fc,stroke:#38bdf8,stroke-width:1.5px
    classDef i fill:#2a1225,color:#ff8fa3,stroke:#ff2d60,stroke-width:1.5px
    classDef e fill:#0d1a0e,color:#86efac,stroke:#22c55e,stroke-width:1.5px
    classDef ui fill:#1a0d24,color:#ce93d8,stroke:#6a1b9a,stroke-width:1.5px
    classDef fix fill:#11111b,color:#cdd6f4,stroke:#00d4aa,stroke-width:1.5px
```

Use the four branches to narrow the next check. Some issues need more than one attempt. The branches map to the systems you can edit: [projects](https://www.taskade.com/learn/projects/databases), [agents](https://www.taskade.com/learn/agents/custom-agents), [automations](https://www.taskade.com/learn/automation/automations-execution), and [styles](https://www.taskade.com/learn/genesis/app-styles).

### Related guides

- [AI Error Recovery](https://www.taskade.com/learn/genesis/error-fixing). Retry, repair, or escalate app errors.
- [A Maker's Guide to AI Prompts](https://www.taskade.com/learn/genesis/prompt-guide). Prompt patterns that prevent most issues.
- [Version History](https://www.taskade.com/learn/genesis/version-history). Roll back to a known-good state while you debug.
- [Taskade EVE Assistant](https://www.taskade.com/learn/agents/eve-assistant). The AI you talk to during troubleshooting.
- [Workspace DNA](https://www.taskade.com/learn/genesis/workspace-dna). Understand the pillars you diagnose.
