Skip to main content

My Agent isn't Behaving as Expected: Common Issues and Fixes

A list of common problems and troubleshooting steps.

Andrija Krstic
Updated by Andrija Krstic
This article offers general guidelines for troubleshooting and resolving issues with the AI Website Builder. If you need additional support, you can contact our team via live chat or, if you’re a community member, through the Slack group.

Important considerations

AI Website Builder is built on top of publicly available LLMs, leveraging their infrastructure to handle and process requests on behalf of the client. Like any other LLM, it is prone to errors, and it’s likely that some level of imperfection will always exist. Keeping this in mind helps foster patience and set realistic expectations when working with the builder.

We tried to summarize some of the most common errors and troubleshooting in this guide which should help you navigate through some of the most common errors

For best practices and guidelines how to properly prompt the builder in an effort to save token burn and produce the best output please refer here.
This list contains some of the general troubleshooting client can take on their behalf. In case initial troubleshooting is not working or is not yielding any results, make sure to contact the support team via support chat or via dedicated Slack workspace (if you have access to it).

Preview problems

Don't try to solve preview problems by prompting AI agent. Problems with previews can't be solved by an AI agent as they are correlated with problems

Error

Preview panel is not loading anything or is being stuck on Connecting to skynet prompt for too long.

Troubleshooting

If the preview is not loading, you can try the following:

  1. Refresh the preview
  2. Start a new chat forking the existing one
  3. Restart the preview server (click on Project Settings - Settings - Restart preview server)

502 Bad Gateway

Error

Troubleshooting

You can try doing the following (and in this order):

  1. Refresh the browser page
  2. Refresh the preview server (after clicking on the Project Settings, choose Settings and then click on Refresh Preview as in the image below).

404 Page Not Found

Error

Troubleshooting

Page you're trying to preview or make changes to was probably deleted or have had slug changed. Troubleshooting should include one of the below:

  1. Clicking Return Home will restart the preview server and will show the last iteration of the site page client was working on
  2. Choosing the root (home) page or any other pre-built page from the drop-down should take you to the page preview of one of the active pages
  3. Revising the code and changing (reverting) some of the page slug changes
Sometimes the slug for the page might end up being changed in the process (eg. changing the page's slug from /products to /products-new. In these instances, you can prompt an agent to manually change or revert the slug to the correct one. You can look up the site structure by looking up the Code Editor and revising the structure of the Components folder.

Element Selector not working

You can read more about Element Selector and how it's working here.

Error

Element Selector is not functioning (it's grayed out and impossible to click on / use)

Troubleshooting

Some of the scripts were (unintentionally) deleted from the code. You can either prompt an AI agent to get them back or you can add them manually (from inside the code editor). This is what needs to be added back and where:

In next.config.ts, add the following code:

experimental: {    ...(process.env.NODE_ENV === 'development' && {      swcPlugins: [['@subbly/swc-plugin-add-element-source', {}]],    }),

In src/app/layout.tsx, add the following code:

<script id="sandbox-messenger" src="https://assets.subbly.co/builder/sandbox-messenger.js" type="module" strategy="afterInteractive" />

In src/app/global-error.tsx add the following code:

<script id="sandbox-messenger" src="https://assets.subbly.co/builder/sandbox-messenger.js" type="module" strategy="afterInteractive" />
Make sure to save the changes if you're adding the code manually through the code editor. If builder returns a runtime error after adding the code, let the AI fix the error by clicking the Fix with AI button.

Runtime Error

Error

Troubleshooting

Let AI agent fix the issue by clicking on Fix with AI. These issues are most likely related with some source components missing or conflicting, AI should be capable of solving these easily.

If it doesn't solve it on the first try and reports the same (or similar) error, repeat the process. If it's persistent, please reach out to support.

Sign in to Code Sandbox

Error

Preview panel is showing Code Sandbox login panel (similar to the one in the picture below)

Troubleshooting

Prompting the agent can't handle/fix this error so don't try that. You'll only burn credits on it without any success in solving for this error.

This error is associated with the fact that the browser is not capable of storing cookies for an iframe. In order to properly troubleshoot this problem, you need to try the following (and in this order):

  1. Prevent cross-site tracking on your browser
Disabling cross-site tracking solves this browser-related problem in large majority of the cases, if that doesn't work, proceed with the troubleshooting below.
  1. Delete all the cookies from the browser's cache associated with the application
  2. Log out of Subbly account
  3. Log back in and restart the builder
If you're using Chrome, see this article how to clear/delete cookies. If you're using Safari, see here.

Memory limit reached

Error

Troubleshooting

Start the new chat by clicking on the New Chat button as indicated in the image above (will create a fork of an existing chat), or by clicking on Start New Chat from the header (as in the image below).

Application error: Client-side exception

Error

This error is frequently presented when the client is trying to target the specific element with the element selector tool.

Troubleshooting

Error is encountered by some unsupported elements included in the build (wrong type formatting). Solution is to select the wrapper around the corrupt element (div instead of an image for example) and instructing an agent to replace the file with the one that has the correct format.

Supported resource formats are presented on hover inside the chat widget as in the image below.

How did we do?

Your First Project: A Step-by-Step Guide

Optimizing for Performance and Credit Usage

Contact