> 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/common-issues.md).

# Common Issues

### Overview

Common issues are behaviors that look like defects but are usually caused by filters, permissions, or stale state.

This page covers fast checks that resolve most “something looks wrong” reports.

### Key Concepts

* **Scope**: Account → Organization → Project context
* **Permissions**: role-based access that affects visibility and edit actions
* **Filters**: view constraints that hide items

### How It’s Used

Use this page when items appear missing, edits do not appear, or navigation feels inconsistent.

Use it before escalation to reduce noise in support requests.

### Benefits

* Faster self-serve resolution
* Cleaner escalation evidence when an issue is real
* Reduced rework caused by working in the wrong scope

### Setup Steps

{% stepper %}
{% step %}

### Items appear missing

1. Confirm Organization and Project scope in breadcrumbs.
2. Clear filters and search again.
3. Confirm the item is not archived.
4. Confirm access permissions allow visibility.

Related: [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)
{% endstep %}

{% step %}

### Edits do not appear

1. Refresh the page to rule out stale state.
2. Confirm the edited field is visible in the current view.
3. Check history for recorded changes when available.

Related: [Comments and History](/collaboration-and-automation/comments-and-history.md)
{% endstep %}

{% step %}

### Unexpected access or permission errors

1. Confirm the correct Account is selected.
2. Confirm access exists at Organization and Project scope.
3. Request support from an Account Admin when roles are incorrect.
   {% endstep %}

{% step %}

### Reports and dashboards look incorrect

1. Confirm filters applied to the dashboard.
2. Confirm Segment Types and Segments are used consistently.
3. Confirm status meanings are consistent across Projects.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Use Save Views for repeatable lists instead of rebuilding filters each time.
* Standardize status meanings to protect reporting integrity.
* Keep Segment Types stable at the Organization level to protect analytics continuity.

### Summary

Most common issues resolve through scope confirmation, filter review, and permission validation.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/troubleshooting/common-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.