Skip to main content
Start with one task that isn’t working: saving an order, opening a client record, or sending a reminder. Note what you did, what happened, and what you expected.

Start here

Closing or refreshing the tab does not stop a request that is already underway. You can lose your connection, open the chat on another device, or switch to another chat and come back. Reopening the chat shows its progress. A chat works on one request at a time. Find unfinished chats later under In-progress chats on workspace home.

Use the detected error

Fix it for me starts a repair using the error Zite detected. It doesn’t consume AI credits. Ordinary chat requests and Improve my app reviews use credits.
Issue building app panel with Show details, Fix it for me, and Retry build controls

When a build error appears, use the detected details to start a fix. Retry build attempts the build again.

After the fix, repeat the task that failed. If the same error returns, add the result to your next message instead of repeating the same request.

Build fails with an out of memory error

If a large app won’t build, or the build keeps failing with an out of memory error, the build ran out of memory. This can happen on very large apps. It is not caused by your plan, credits, or usage limits. It is not something wrong with what you built. Do not keep retrying the build or pressing Fix it for me. That will not help. Contact support@zite.com or start a chat from the help bubble, and we will sort it out.

Describe a problem clearly

Include the page or workflow name, the steps to reproduce it, and any error message. Add a screenshot for a visual problem.
On the Orders page, I select Submit. The order is saved, but the confirmation email doesn’t arrive. This happens in preview and the published app. Check the latest Submit Order run and explain the failed step before making changes.
For a general check, select +, then Improve my app, then Review agent. For appearance or keyboard-use issues, choose Design agent or Accessibility agent. See Improve my app for what each does.

Common issues

Refresh the editor or reopen the app from workspace home. If it still fails, try another browser or a private window to check whether the problem is browser-specific.If it happens across browsers or devices, contact support with the app link, exact error, and when it started. You don’t need to keep repeating the same checks.
The first time an app or one of its actions is used after a quiet spell, Zite has some extra work to do before your app’s code runs. It loads the published version of the app, checks who is signed in, and fetches connection details and credentials. Zite keeps these ready for a while afterwards, so the next requests are faster.You can see this in Workflow Runs. Open a run and look for the Setup step, described as Fetching metadata, auth, and credentials. It shows how long this took. The run’s total time includes Setup as well as the time your code took.The editor works in a similar way. If you leave it idle, its build environment stops, and your next action waits a moment while it starts again.If Setup is long on every run, not only the first one after a break, describe it in chat with a recent run so Zite can look into what the app loads.
Open Workflows, select the workflow, then History. Find the failed run and expand its steps.
  • Check the inputs and the first failed step.
  • Confirm the connected account and destination are correct.
  • If Zite asks you to reconnect a service, follow that prompt.
Check which actions completed before trying again. A retry could send another email or create another record. A timeout alone doesn’t tell you why the run failed.
Open the workspace database and check the table directly. If the record is there, check the app’s filters and the person’s access. If it is missing, inspect the workflow that should have saved it.For import problems, note the file type, file size, destination, and the step that fails. For deleted data, see Database backup and restore.
Open the app’s ⋯ menu and choose Version history. Inspect the earlier working version. Review the restore confirmation before proceeding.For a smaller fix, tell Zite when it last worked and what changed. After restoring or fixing, test the affected task and publish when ready.
This message in the builder chat is not about your organization’s API key in Developer settings. Regenerating that key will not fix it.The cause is not confirmed. Contact support@zite.com or use the help bubble. Include the app and roughly when it happened.
Last modified on November 17, 2026