Troubleshooting and support

Start with the visible state

Use the page's Retry action once and read the complete error. If several Amazi pages fail together, check the connection and sign in again if the session changed or expired. A maintenance notice can pause new agent submissions until the platform is available. Do not repeatedly start the same destructive or paid action while its first result is still unknown.

Agent or project initialization

During maintenance, you can send messages in an existing project: they are saved to its queue. The queue's Steer active agent button is unavailable. Drafts and queued messages are saved; queued work resumes automatically after maintenance ends. You do not need to resubmit waiting messages. New-project creation and replies to pending agent questions remain paused.

If the agent does not start, check:

• the credit balance;
• your project role;
• an unanswered question from Amazi;
• whether another project task is active.

New messages wait in the shared queue while one task runs. A disconnected integration opens a secure form; never answer it by pasting a credential into chat. During initial application setup, Preview can remain pending while files, dependencies, and the baseline version are prepared.

Preview, environment, and publishing

For Preview, confirm the selected application and wait for current preparation or restart work, then ask the agent to inspect build and runtime health. For a variable problem, verify its name, source, application kind, and whether a production update was published. For a failed release, refresh production status before retrying. For a domain, copy the exact TXT and A or CNAME records, disable DNS proxying during verification, remove conflicting records such as AAAA, and allow propagation time.

For a gateway error, an embedded-only failure, or an old project thumbnail, follow Preview troubleshooting.

Access problems

Project actions depend on role, owner state, email verification, and sometimes the owner's plan. Ask the owner or a Full access member to review membership and project state. Archived projects are owner-only. If access changed while a workspace was open, Amazi can remove the cached project and return you to Projects; request access again instead of relying on an old Preview capability.

Contact support

You can ask Support to consult another project you own, including its chat history. Shared membership and an unfinished ownership transfer do not grant this access. Support stays within diagnosis; request implementation in project chat.

Open Support to search Help or start a case with Amazi Support. Choose a conversation from the Active or Resolved list, or select New case to open a draft. The case is created after you send the first message. Use @ to add an attached image, a project you own, or Amazi Documentation; / offers the sound setting. Describe the issue directly and name the project in your message if needed; there is no project selector. The Support agent can inspect projects you currently own. It is instructed to inspect only the evidence needed for diagnosis: safe project and application state, recent project chats, workspace files, Git history, integration metadata, environment-variable names and status, processes, and logs. It must not change the project or reveal secret values. If diagnosis requires privileged intervention or cannot be completed safely, the case can be handed to an operator.

Attach a screenshot or supported file directly to the case. Support can inspect the attachment even when your message does not name a project.

Closed support conversations remain readable. Their message input and action buttons stay visible but disabled, with the conversation status explained inside the input.

When you write, include:

• the project name and attempted action;
• the complete visible error and approximate time;
• a safe screenshot or diagnostic detail when it helps explain the problem.

Never include secrets: passwords, session tokens, API keys, integration credentials, or secret environment values.