> AI agents: this is one page from Mammoth Analytics documentation. The index of all pages as Markdown is https://docs.mammoth.io/llms.txt. Append `.md` to any docs URL, or send `Accept: text/markdown`, to get Markdown.

# Troubleshooting

> Find the right Mammoth troubleshooting guide by symptom, run a quick diagnostic checklist, learn what the Activity Log records, and contact support.

This section covers common Mammoth problems with a symptom, cause, and fix for each. It is for anyone who builds pipelines, connections, automations, or dashboards. To start, find your symptom in the table below.

## How to use this section

Each guide focuses on a specific problem area. Start with the guide that matches your symptom:

| I'm seeing… | Start here |
| --- | --- |
| Dashboard not loading, wrong data, chart errors | [Dashboard issues](https://docs.mammoth.io/learn/troubleshooting/dashboard-issues) |
| Data looks wrong, duplicates, null values, quality score low | [Data quality issues](https://docs.mammoth.io/learn/troubleshooting/data-quality-issues) |
| A specific error message or HTTP status code | [Error messages reference](https://docs.mammoth.io/learn/troubleshooting/errors) |
| Slow queries, pipelines timing out, reports taking too long | [Performance issues](https://docs.mammoth.io/learn/troubleshooting/performance-issues) |
| Transformation step failing, pipeline not producing expected output | [Transformation errors](https://docs.mammoth.io/learn/troubleshooting/transformation-errors) |
| Connection authentication failed, data not refreshing | [Connection troubleshooting](https://docs.mammoth.io/learn/troubleshooting/connection-troubleshooting) |

## Quick diagnostic checklist

Before diving into a specific guide, run through this checklist—it resolves a large fraction of common issues:

1. **Check platform status**—Visit <https://status.mammoth.io> to confirm there are no active incidents or degraded services.
2. **Check the Activity Log**—Open the **Activity Log** for your workspace or project to see who changed what and when. It records changes to your data and configuration, not errors. See [What the Activity Log captures](#what-the-activity-log-captures) below for scope details.
3. **Look for error indicators**—Pipeline errors appear as a **This pipeline has errors** banner on the pipeline, and a failed automation shows an **Error** status with the failure in **Last run result**. Neither appears in the Activity Log.
4. **Try a hard refresh**—Press `Ctrl+Shift+R` (Windows/Linux) or `Cmd+Shift+R` (Mac) to bypass browser cache.
5. **Check your permissions**—Confirm you have the correct role for the action you're trying to take (Project Admin or Project Editor).

## What the Activity Log captures

The Activity Log is your audit trail for **changes**—it is not an error log.

**The Activity Log DOES capture:**

- Dataset create, edit, rename, and delete events
- Combine, replace, and duplicate dataset operations
- Pipeline task changes
- Connection changes
- Automation edits and batch suspends
- Workspace invitations

**The Activity Log does NOT capture:**

- Connection authentication failures (expired tokens, invalid credentials)
- Pipeline task-level errors (individual task failures within a pipeline)
- Schema mismatch errors during data import

For these errors, check the **error indicators** shown directly in the interface on the affected connection, pipeline, or automation.

## Troubleshooting guides

### [Dashboard issues](https://docs.mammoth.io/learn/troubleshooting/dashboard-issues)

Diagnose blank dashboards, charts showing wrong data, AI generation failures, sharing permission errors, and mobile display problems.

### [Data quality issues](https://docs.mammoth.io/learn/troubleshooting/data-quality-issues)

Understand Mammoth's six-dimension quality framework, interpret quality scores, and fix the most common data quality problems: duplicates, missing values, outliers, and type mismatches.

### [Error messages reference](https://docs.mammoth.io/learn/troubleshooting/errors)

A reference for the errors and HTTP status codes Mammoth returns, with the cause and fix for each.

### [Performance issues](https://docs.mammoth.io/learn/troubleshooting/performance-issues)

Diagnose slow dashboards, slow transformation pipelines, and query timeouts. Includes optimization strategies for large datasets and scheduled automations.

### [Transformation errors](https://docs.mammoth.io/learn/troubleshooting/transformation-errors)

Fix common errors in visual pipeline transformations: type mismatches, missing columns, math expression errors, and join key conflicts.

### [Connection troubleshooting](https://docs.mammoth.io/learn/troubleshooting/connection-troubleshooting)

Resolve authentication failures, expired credentials, network connectivity issues, and schema mismatch errors for your connections.

Hitting a size, row, or schedule limit? See [Limits and quotas](https://docs.mammoth.io/learn/limits-and-quotas). For common how-to questions, see the [FAQ](https://docs.mammoth.io/learn/faq).

## Emergency quick reference

If you're in a critical situation:

| Situation | Action |
| --- | --- |
| Platform outage or degraded service | Check <https://status.mammoth.io> |
| Data emergency—need immediate help | Email [support@mammoth.io](mailto:support@mammoth.io) with your workspace ID and a description |
| Authentication locked out | Email [support@mammoth.io](mailto:support@mammoth.io)—include your user email and workspace name |
| Data corruption suspected | Suspend your scheduled automations immediately, then contact [support@mammoth.io](mailto:support@mammoth.io) |

> **Note on failed automations:** Fix the root cause of a data or authentication failure first, then use **Run now** on the automation to re-run it.

## Contacting support

If you've worked through the relevant guide and still can't resolve the issue:

- **Email:** [support@mammoth.io](mailto:support@mammoth.io)
- **What to include:** Your workspace name, the feature area (connection, pipeline, dashboard), steps to reproduce the issue, and any error messages you've seen.

![In-app support chat window opened from the sidebar, with a Send us a message button](https://docs.mammoth.io/api/v1/images/20260428_141126_Screenshot2026-04-27110606.jpg)

## Automation scheduling

How often an automation can run depends on your plan. See [Scheduling](https://docs.mammoth.io/learn/automations/scheduling) for the frequency options, and contact [support@mammoth.io](mailto:support@mammoth.io) if your workflow needs a more frequent schedule than your plan allows.

---
Source: https://docs.mammoth.io/learn/troubleshooting.md · Updated: 2026-10-13