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

1

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

2

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

3

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.

4

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.

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.