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

# Read Mammoth failure notifications and alerts

> What Mammoth's failed export, data pull, watched-folder file and data check notifications mean, who receives each one, and how to act on them.
>
> Applies to: Roles: Workspace members, in Build mode. Where: Left sidebar › Notifications (bell)

When an export, data pull, watched-folder file or data check you started or own fails, the [notifications bell](https://mammoth.io/docs/learn/automate/notifications/) at the bottom of the left sidebar tells you why. A failure has a red error icon, and most have a button that takes you to the item to fix.

## Read export and data pull failures

When an export you ran fails, the bell shows why. A failed export doesn't pop up as a toast: it waits in the bell.

| Message | What it means |
| --- | --- |
| "Exporting to PostgreSQL failed." (also MySQL, AWS Redshift, SFTP, Elasticsearch) | The destination refused or couldn't be reached |
| "Exporting orders from Sales_View 1 to Google BigQuery failed." | A BigQuery export failed |
| "Publish DB export failed." | Publishing to a Mammoth Managed database failed |
| "Token has been expired or revoked." | The saved connection needs signing in again |
| "Storage quota exceeded." | Your workspace is out of storage |
| "Dataset Sales 2026 no longer exists." | The destination dataset of a Send to Dataset was deleted |
| "Dataset March could not be appended to Sales 2026 due to mismatch in column name or types." | The columns don't match the destination |
| "Unable to pull data. No matching file found for the given pattern." | A file pull found no file matching its pattern |
| "Oops! Something went wrong!" | Mammoth couldn't name the cause. Check the export or pull settings and try again |

## Find out why a file didn't go in

When an automation watches a folder and a file dropped there doesn't go into its destination dataset, Mammoth tells two people: whoever added the file, and the automation's owner. A file nobody added by hand (for example, one collected from cloud storage) tells only the owner.

| Text | When |
| --- | --- |
| "Dec_sales.csv didn't go into Sales 2026" | The file failed. The reason follows, for example "Couldn't be read" |
| "Dec_sales.csv was kept separate from Sales 2026" | The file was kept apart from the dataset rather than added |
| "Dec_sales.csv wasn't added to Sales 2026" | The file was not added for another reason, given after it |
| "Dec_sales.csv and 4 more files weren't added to Sales 2026. The folder says why for each." | Several files of one run didn't go in. You get one notification, not one per file |

Click **Open the folder** to go to the folder, where each file's row says why it didn't go in. The same files show in Monitor under **Needs Attention** > **Automations**. See [Fix files a watched folder didn't add](https://mammoth.io/docs/learn/automate/watched-folder-files/#fix-a-file-that-didnt-go-into-the-dataset).

## Act on a failed data check alert

A Data Check in a pipeline is tested after every run. When a check goes from passing (or never run) to failing, its owner gets one notification, and a toast with **Open the view** if they're in the app. The notification names the check, the dataset and View, and what failed, for example "“Late deliveries” failed on orders.csv › View 1: Matching rows: 14, expected: <= 10".

You get one notification when the check starts failing, not one per failing run. A check made by the system, with no owner, notifies nobody. Click **Open the view** to open the View in the Data Editor.

The check's **Notify on failure** email is separate and is set on the check itself. See [Remove duplicate rows and add data quality checks](https://mammoth.io/docs/learn/clean-and-shape/duplicates-and-checks/).

## Related

- [Notifications](https://mammoth.io/docs/learn/automate/notifications/): open the bell, mark items read and clear them.
- [Fix files a watched folder didn't add](https://mammoth.io/docs/learn/automate/watched-folder-files/): fix each waiting file.
- [Send data to a database or BI tool](https://mammoth.io/docs/learn/share-and-export/send-to-destinations/): export settings.
- [Combine files dropped in a folder](https://mammoth.io/docs/learn/automate/consolidate/): the watched folder behind file alerts.

---
Source: https://mammoth.io/docs/learn/automate/failure-alerts.md · Updated: 2026-11-08