Notifications
The notifications bell tells you when something you started or own in Mammoth finishes or fails: an export or download, a data pull, a file a watched folder didn't add, a data check that started failing. This page explains where to find the bell, what each notification says, and how to clear them. For the live state of a whole project, use Monitor instead.
Open the notifications bell
Click the bell icon (Notifications) at the bottom of the left sidebar. On a phone, open the more menu in the bottom tab bar and choose Notifications. The panel opens beside the sidebar.
- A dot on the bell means you have something new. It clears when you open the panel.
- The panel header reads Notifications, with a count of unread items next to it.
- New notifications arrive while you work. You don't need to reload the page.
- With nothing to show, the panel reads "All caught up!" and "No notifications for now".
Each notification shows your workspace name, what happened, and how long ago (for example "5 minutes ago"). A job that is still running shows a progress bar instead of a time. A failure has a red error icon.
Who sees the bell
| Who | Bell |
|---|---|
| Workspace members in Build mode | Shown |
| Workspace members in Ask mode | Not shown. Notifications live in Build |
| People with no workspace of their own, who only open dashboards shared with them | Not shown |
| Anyone not signed in (for example, on a public dashboard link) | Not shown |
| A workspace that is still being set up | Shown but disabled until it is ready |
Read, unread and clear
| Control | What it does |
|---|---|
| Click a notification | Marks it read. If it has an action (such as Download or Open the view), it also does that |
| Tick icon (on hover) | Marks one notification read, or unread again |
| x icon (on hover) | Removes that one notification |
| Mark all read | Marks every unread notification read. Shown when you have unread items |
| Delete read | Removes every notification you've already read. Shown when you have read items |
What each notification means
| Notification | Example | Click it to |
|---|---|---|
| Download ready | "Urgent tickets.csv is ready" | Download the file again |
| Export failed | "Exporting to PostgreSQL failed." | Read the message |
| Data pull failed | A message that the data pull for a dataset (for example Orders) from its connector has failed | Read the message |
| A file didn't go in | "Dec_sales.csv wasn't added to Sales 2026. Couldn't be read" | Open the folder |
| A data check failed | "“Late deliveries” failed on orders.csv › View 1" | Open the view |
| Dashboard audience | "Sales review had its busiest week: 120 views, up from 45." | Open Audience (or Open dashboard when a colleague published it) |
| Your data for a template | "Your data is ready for Sales review. Review your version." | Open dashboard |
| A live chart needs fixing | "Sales review needs fixing: its data changed shape. Embeds show the last good chart." | Fix the chart |
The sections below cover the ones you're most likely to act on.
Download ready
A download that takes a while (for example, several datasets downloaded at once from the Data Library) runs in the background. While it runs, a toast reads, for example, "Preparing Urgent tickets as CSV…". When the file is ready, the toast changes to "Urgent tickets.csv is ready" with a Download button.
If you stay on the page that started the download, that page saves the file itself and no toast appears. If you leave that page first, the toast appears instead. Either way, the finished download stays in the bell, so you can click it and choose Download later. A view's name is left out when it is a default name such as "View 1", so the file is named after the dataset.
For download formats and limits, see Download options.
Export and data pull failures
When an export you ran fails, the bell shows why. Common messages:
| 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 |
A failed export doesn't pop up as a toast. It waits in the bell. For export settings, see Send to destinations.
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 also show in Monitor under Needs Attention > Automations. See Monitor.
A data check failed
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.
Agent notifications
The in-app Agent (available on Enterprise plans) adds an Agent group at the top of the panel, above a Data group with everything else. It lists what the Agent finished or is waiting on, such as "Alert: Late deliveries above 10" with Open Today, a run that needs you with Open chat, or a finished file with Download. Items waiting on you come first.
Troubleshooting
I don't see the bell.
You're in Ask mode, you have no workspace of your own (you only open dashboards shared with you), or you're not signed in. Switch to Build mode if you have it.
A download toast disappeared before I clicked it.
Open the bell. The "is ready" notification stays there with Download until you remove it.
A notification I expected never arrived.
Some go to one person only. For example, only the owner of a data check is told when it fails, and live link updates don't send notifications.