Skip to main content

Documentation Index

Fetch the complete documentation index at: https://zite.com/llms.txt

Use this file to discover all available pages before exploring further.

Most issues are easier to fix when you can identify what changed, where the issue appears, and what should happen instead. Start with the Zite tools below before trying to rewrite the same prompt.

​
Start here

If this is happeningUse this first
Zite detected an errorClick Fix it for me in the toast or chat message.
You want Zite to inspect the appOpen Improve my app and choose Review.
The app works but needs visual polishOpen Improve my app and choose Designer.
You are not sure what is wrongSwitch to Chat mode and ask Zite to explain before changing anything.
The fix is large or unclearUse Plan mode to break the work into steps.
A recent edit broke the appRestore a working version from history.
Fix it for me is free and does not consume credits.

​
Zite-specific issues

Click Fix it for me first. Zite will use the error details it already detected to diagnose and repair the issue.If the same error appears again, switch to Chat mode and ask:
The automatic fix did not resolve this. Explain what is still failing and suggest the smallest next fix before changing anything.
Use Improve my app when the problem is broader than one obvious error.
  • Review scans the app for common issues and fixes them.
  • Designer explores the running app, captures screenshots, and polishes the look and feel. It can take longer.
Use Review for broken behavior, missing states, and general quality checks. Use Designer when the app works but feels visually inconsistent.
Try these in order:
  1. Refresh the page.
  2. Re-open the app from your dashboard.
  3. Try a private or incognito browser window.
  4. Disable browser extensions that may block scripts.
  5. If this started after a recent edit, restore a previous version from history.
  6. If there is an error message, paste it into Chat mode and ask Zite to investigate.
If the issue only happens in the published app, test from another browser or device to rule out local caching.
No app created yet is usually a temporary connection or creation issue.
  • Refresh the page.
  • Go back to your dashboard and re-open the app.
  • If the app still does not load, start a new prompt or contact support.
Too many requests and Timeout errors usually mean too many changes were requested in a short time, or an external service took too long to respond.
  • Wait a few minutes and try again.
  • Re-open the app.
  • Break the request into smaller steps.
  • Check whether the error came from Zite or an external integration.
Retry the build or refresh the page. Changes made before the error are automatically saved, so you will not lose edits that were already applied.This can happen because of a third-party sandbox provider issue. The Zite team is working on ways to reduce the impact of this error.
Use history to restore a working version, then make the next fix in a smaller step.Before rebuilding, ask Zite:
This worked before the last change. Compare the current version with the previous working version and explain the likely cause before making a fix.

​
Common building issues

Upload a screenshot and describe the exact issue. If possible, use Selective Edits to highlight the element before asking Zite to change it.Keep the request small: one section, one page, or one interaction at a time.
On the Orders page, the Submit button is too low and overlaps the footer on mobile. Fix only this button layout and keep the rest of the page unchanged.
Tell Zite what you clicked, what happened, and what should happen instead.
On the Orders page, the Submit button should save the form and show a success message. Right now, clicking it does nothing. Inspect the button and save flow, then explain the issue before fixing it.
Large prompts are more likely to produce partial results.
  1. Ask Zite to summarize what it changed.
  2. List what is still missing.
  3. Ask for one remaining change at a time.
  4. Use Plan mode for larger updates before building.
Only update the customer detail page. Add a status badge next to the customer name and make sure it uses the Status field from the Customers table. Do not change the dashboard or navigation.
Start with workflow run history. It shows the trigger, inputs, steps, outputs, and errors.Useful prompts:
Look at the latest failed run for this workflow and explain which step failed and why.

This workflow should create a customer record and send a Slack message. It creates the record but does not send Slack. Check the run history and suggest the smallest fix.
Check the app is connected to the right Zite Database, table, and fields.Also check:
  • field names and field types match what the app expects
  • imported data columns were mapped correctly
  • workflows writing to the database have the expected inputs
  • AI fields with failed cells show clear regenerate errors from the field header
Zite’s built-in database can make app behavior easier for the agent to understand and can reduce errors from external data sources.
First identify whether the issue is in Zite or the connected service.Check:
  • the connected account is still authorized
  • the workflow step has the required input values
  • the external service is available
  • any required API key, token, or secret is still valid
  • the run history shows the exact failed step
If the same workflow works with Zite Database but fails with an external service, the issue is usually in the integration setup, account permissions, or external service response.

​
Prompting tips

  • Name the exact page, section, database table, workflow, or integration.
  • Include screenshots for UI problems.
  • Include error messages and workflow run details when available.
  • Ask Zite to explain before fixing when the cause is unclear.
  • Keep fixes small: one issue, one area, or one workflow at a time.
  • Avoid repeating the same fix prompt if it did not work. Switch to Chat mode or Plan mode and ask for a different approach.

​
Need more help?

Still stuck? Try this:
  1. Use Plan mode and ask Zite for a step-by-step fix plan.
  2. If the issue started after a UI or feature change, revert to a stable version from history.
  3. If you need support, contact support@zite.com or start a chat from the help bubble.
Include the app link, what you were trying to do, the exact error message, screenshots or a screen recording, and what changed before the issue started.

Related topics

Recover Old VersionWorkflow Run HistorySelective EditsAgent ModesZite Database
Last modified on May 18, 2026