> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/troubleshooting/error-messages.md).

# Error Messages

### Overview

Error messages indicate a failure to load, save, or access content.

This page standardizes what evidence to capture and how to triage by category.

### Key Concepts

* **Error text**: message shown in the UI
* **Error code**: numeric or short identifier when provided
* **Timestamp**: time of the error with time zone
* **Scope**: Account, Organization, Project, and page context

### How It’s Used

Use this page when a reproducible error occurs and escalation is likely.

Use it to capture evidence that support can act on quickly.

### Benefits

* Faster support triage
* Reduced repeated troubleshooting loops
* Better audit trail for production-impacting issues

### Setup Steps

{% stepper %}
{% step %}

### Capture the evidence set

Capture:

* exact error text (copy/paste)
* error code (if present)
* timestamp and time zone
* scope (Account, Organization, Project, page)
* screenshot with sensitive data redacted
  {% endstep %}

{% step %}

### Triage by category

Common categories include:

* **Access errors**: authentication or authorization failures
* **Not found errors**: item deleted, moved, or scope mismatch
* **Timeouts**: network delays or load issues
* **Server errors**: transient errors that may resolve after retry

If the category is unclear, escalate with captured evidence.
{% endstep %}

{% step %}

### Apply a safe retry pattern

1. Refresh the page once.
2. Retry the action once.
3. Avoid repeated rapid retries to prevent rate limiting.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Include at least one reproduction step sequence for support.
* Prefer permalinks to the affected item when available.
* Avoid sharing secrets in screenshots or recordings.

### Summary

Error resolution is fastest when evidence includes text, timestamp, scope, and reproduction steps.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/troubleshooting/error-messages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.