> 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.

# See when a Mammoth export runs and check its history

> See what sets a Mammoth export off and when it runs next, limit email exports to once a day or week, read the run history and get failure emails.
>
> Applies to: Where: View › Export › an export step › When it runs and Run history

Every saved export shows what sets it off, when it runs next and how its recent runs went. Open the export step from the pipeline panel: **When it runs** sits under the form and the run history at the top. Project members get an email when an export fails.

## See what sets an export off

Export forms with an **Apply** button have a **When it runs** box under the form. Send to Dataset, the managed databases and **Somewhere else…** don't.

| What you see | What it means |
| --- | --- |
| "When new data is added to" the Dataset | The export runs when someone uploads a file, or a folder automation appends one |
| "After" the Dataset "refreshes" | A Dataset Refresh automation refreshes the data on a schedule, and the export runs after each refresh. The box shows the schedule and the next run. Click **Change in Automations** to edit that automation |
| **Only when someone changes this data** | Nothing refreshes the data on its own, so the export could stay quiet for weeks. Click **Refresh it on a schedule** to create a Dataset Refresh automation, or **Send it on a schedule** (saved exports) to create a Scheduled Export |
| A schedule row, such as "Every week on Monday at 9:00 AM" | A Scheduled Export automation also runs this export on a clock. Click **Change in Automations** to edit it |

When a Scheduled Export runs the export, the box has an **Also send after each data update** checkbox. Clear it to send only on the schedule. If nothing sends the export, the box warns "Nothing sends this export on its own now." with a **Run after each data update** link. If the box can't load, it says "Couldn't load what sets this export off. It still runs as saved."

For the automations themselves, see [Refresh a dataset](https://mammoth.io/docs/learn/automate/refresh-a-dataset/) and [Export on a schedule](https://mammoth.io/docs/learn/automate/scheduled-export/).

### "This export's schedule moved to Automations"

Exports used to keep their own schedule. One that had one now shows **This export's schedule moved to Automations**: it still runs on the same schedule, as a Scheduled Export automation.

- **Keep the schedule** hides the note and leaves the schedule as it is.
- **Run after each data update instead**: after you click **Apply**, the export runs after each data update and leaves the Scheduled Export.

## Limit how often an email export sends

An email export that sends after data updates has a **Send at most** choice, so a busy dataset doesn't flood inboxes.

| Option | What it does |
| --- | --- |
| **Every time** (default) | Sends each time the data updates |
| **Once a day** | Holds updates and sends at the time you pick (half-hour steps, your local time) with the newest rows. If nothing changed since the last email, it sends nothing |
| **Once a week** | The same, on the weekday and time you pick |

While updates are held, the box shows "Holding changes since" a date and time. **Send at most** only limits sends that follow data updates: a Scheduled Export that includes the email still sends on its own schedule.

## Check an export's run history

Open a saved export step to see its runs at the top of the form.

- The first line shows the last run, such as "Last run 2 hours ago", or "Last run failed 2 hours ago" with the error underneath.
- **Run history** lists the 20 most recent runs: date and time, what started it (**Manual**, **Pipeline** or **Schedule**), the destination, rows sent and how long it took. Hover a failed run to read its error. **Hide history** closes the list.
- Email runs say who they reached: "Sent to 3 people", "Skipped: no rows, so nothing was sent", or which people it couldn't reach.

A new export shows "No runs yet". If the history can't load: "Run history is unavailable right now".

## Get an email when an export fails

When an export fails, Mammoth emails everyone with access to the project. The subject names the export, the Dataset and the View. The same goes for a failed pipeline task.

Scheduled runs send one email per failure streak: if a scheduled run fails again before a successful run, no new email is sent. A failure in a run that isn't scheduled always sends one.

## Pause exports while you edit the pipeline

When you apply a pipeline change to a View that feeds exports or published dashboards, Mammoth asks whether to pause those sends while you work. See [Pause sends while you edit](https://mammoth.io/docs/learn/clean-and-shape/pause-sends/).

## Related

- [Set up an export](https://mammoth.io/docs/learn/share-and-export/send-to-destinations/): set up an export and send only new rows.
- [Hold exports for review](https://mammoth.io/docs/learn/share-and-export/hold-exports-for-review/): Auto-sync, the Monitor panel and troubleshooting.
- [Export on a schedule](https://mammoth.io/docs/learn/automate/scheduled-export/): send exports at fixed times.
- [Refresh a dataset](https://mammoth.io/docs/learn/automate/refresh-a-dataset/): the automation that sets most exports off.

---
Source: https://mammoth.io/docs/learn/share-and-export/export-runs-and-history.md · Updated: 2026-11-08