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

# Monitor running, failing and paused pipelines

> Use Mammoth Monitor to see what needs attention, what is running or stuck, and what has Auto-sync paused in a project, then fix errors and approve Checkpoints.

Monitor shows what is happening in a Mammoth project right now: items waiting for your action, pipelines and automations running, items with Auto-sync paused, and the Activity Log. Click **Monitor** at the bottom of the left sidebar. The orange badge on it counts the items in **Needs Attention**, so start there if you see it.

![Monitor for the Sales Data project, Needs Attention tab, with an Errors section and Pending items each showing a Fix settings button](https://mammoth.io/docs/images/20260805_045831_M-needsattention1.webp)

## Open Monitor and switch projects

Click **Monitor** in the left sidebar, from any project. The orange badge shows the count of items in **Needs Attention**. It appears when one or more items need attention, and disappears when all are resolved (or when you can't see any of them). It updates with each refresh.

![Left sidebar with Data and Publish items and a Monitor item at the bottom showing an orange badge with the number 20](https://mammoth.io/docs/images/20260805_045846_M-orangebadge1.webp)

The project selector next to the Monitor title lets you view any project you have access to. Switching here does **not** change the project you are working in. It is a read-only view into that project's live state.

![Monitor project selector dropdown open, listing projects including P2, Test App, Sales Data, and Marketing, with Sales Data checked](https://mammoth.io/docs/images/20260805_045907_M-swithcingproject1.webp)

### Who can open Monitor

| Condition | What happens |
| --- | --- |
| View-only workspace | Monitor sidebar item disabled |
| Guest or anonymous user | Monitor hidden entirely |
| Workspace not yet prepared | Monitor sidebar item disabled |
| No projects you belong to | Monitor sidebar item disabled |
| No **View Activity Log** permission | Activity Log tab not shown |

## The four Monitor tabs

| Tab | Badge colour | What it shows |
| --- | --- | --- |
| **Needs Attention** | Orange | Items needing your action: errors, pending data, pipeline drafts, automation files, retentions, governance |
| **Running** | Green | Pipelines, tasks and automations running or queued, plus Active Retentions. The count includes Active Retentions |
| **Paused** | Grey | Pipeline tasks, exports and connections with Auto-sync off |
| **Activity Log** | None | Chronological event history for the project or workspace |

The badge colour is a secondary cue: each tab also shows its name and count.

### How often Monitor refreshes

| State | Interval |
| --- | --- |
| Monitor open | Every 5 seconds |
| Monitor closed (in the background) | Every 45 seconds |

Polling returns to every 5 seconds as soon as you go back to Monitor. Items that finish between polls disappear on the next refresh. This is expected.

## Act on items in Needs Attention

The tab has up to five sections: **Errors**, **Pending**, **Automations**, **Pending Retentions** and **Governance**. Each appears only when it has items. Error, Batch pending, Pipeline changes pending and Governance rows also have a **Show in workflow** icon button that opens the View's workflow. Other rows have none.

With nothing to do, the tab shows a checkmark, "All clear" and "Nothing needs attention right now."

![Needs Attention tab with Pending items, a Pipeline changes pending row, and a Governance section with a Checkpoint: approval required row](https://mammoth.io/docs/images/20260805_045931_Needsattentionwiththreesection1.webp)

### Fix pipeline errors

Each row reads "Error running pipeline", with the dataset name, View name and task count. Click **Go to View** to open the View in the Data Editor and inspect the error. If the View was deleted, Monitor shows "View is missing or was deleted." See [Fix a failing step](https://mammoth.io/docs/learn/clean-and-shape/fix-a-failing-step/).

### Apply pending batches and updates

**Batch pending** means new data has arrived at a destination and is waiting to be applied. The row shows "Batch pending", the source View name, "New batch received 5 minutes ago", the row count and the destination or operation (for example `Join: Orders 2026` or `Source: Sales`).

| Action | What it does |
| --- | --- |
| **View Batch** | Previews the incoming data before you commit it (when the destination is a dataset) |
| **Update** | Applies the batch now. A spinner shows while it runs, and the row disappears when done |
| **Copy link to clipboard** | For Live Link destinations only: copies the live link URL to share |

A Batch pending item appears when a Join or Lookup source View receives new data, a connector export or Publish-as-Database destination receives new data, a cross-project dependency's source updates, or a Live Link's external source changes. When the source link has Auto-sync off, the batch is held: the row reads "new batch received, auto-sync off" and shows **Preview** and **Process** instead. Items clear when the destination is updated or Auto-sync is turned back on.

Other pending items that need your input appear in the same section: **Ambiguous date format**, **Password required** (a password-protected file), **Schema mismatch**, **Sheet selection required** and **Unstructured rows**. Each has a button such as **Select sheets**, **Fix batch settings** or **Fix settings** that takes you to the item.

**Update pending** means a destination that isn't a dataset (for example an export) has new source data. The row shows the View name, row count and export type (for example *66,943 rows · Export: MySQL*). Click **Update** to run it now. The row can also show **Copy link to clipboard** for a Live Link. After a successful update, a toast reads "Update data".

**Pipeline changes pending** means a pipeline has draft changes not yet applied. The row shows the dataset, View name and task count (for example *6 tasks ready to run*). Pipelines with errors come first. Click **Go to View** to review or apply the changes.

If an update fails for some items, a toast reads "Some of the pending items could not be updated. Please verify them." Check each item on its own.

### Review files an automation couldn't add

The **Automations** section lists files that an automation's rule sent to a dataset but that didn't go in, and that nobody has dealt with yet. A row reads **File didn't go in** (red icon) or **File kept separate** (amber icon), with the folder, file name and reason, for example "Couldn't be read" or "Didn't go into Sales 2026". Click **Review** to open the file in the Data Library.

The person who added the file and the automation's owner also get a [notification](https://mammoth.io/docs/learn/automate/notifications/#find-out-why-a-file-didnt-go-in). A file whose columns don't fit is listed under **Pending** instead. A duplicate isn't listed: it shows in its folder and the automation's History. 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).

### Approve pending retentions

Data retention policies waiting for approval show the notice "These actions will permanently delete or suspend data once approved. Review each policy carefully before approving." Rows are labelled "pending deletion" or "pending suspension". Use **Review and Approve** to inspect and approve each policy.

### Approve Checkpoints and review failed data checks

The **Governance** section appears when pipelines are paused at approval gates or data checks have failed. These items count toward the badge.

| Item | Row detail | Action |
| --- | --- | --- |
| **Checkpoint: approval required** | Dataset · pipeline name · "Task 2 of 5 is waiting for approval" | **Approve** |
| **Data check failed** | Dataset · pipeline name · "1 of 3 checks failed" | **Review** |

Checkpoints and data checks are tasks in the pipeline. The owner of a data check also gets a notification the first time it fails. See [Pause a pipeline for approval with a Checkpoint](https://mammoth.io/docs/learn/clean-and-shape/checkpoints/) and [Remove duplicate rows and add data quality checks](https://mammoth.io/docs/learn/clean-and-shape/duplicates-and-checks/).

## See what is running now

The **Running** tab lists all pipeline Views, export tasks and automations running or queued. With nothing running and no Active Retentions, it shows a checkmark, "Nothing running" and "No tasks are processing right now."

When rows are present, a banner appears at the top:

| Banner | Meaning |
| --- | --- |
| **Executing** (green dot) | Tasks are running and progressing normally |
| **Stuck** (red dot) | One or more tasks have run past their thresholds. The banner reads "All active pipeline and export tasks across the workspace appear here. Tasks that have been running for an unusually long time may be marked as stuck." |

Each row shows the item name (a link to open it in the Data Editor), a status pill and detail text. Pipeline rows also have a **Show in workflow** icon button. Task and automation rows don't, and automation names aren't links.

| Status | What it means |
| --- | --- |
| **Queued** | Waiting for a worker. It starts automatically |
| **Executing** | Processing right now |
| **Waiting for Worker** | No worker is free |
| **Registering Lock** | Taking a resource lock before processing |
| **Waiting for Lock** | Another task holds the lock. It starts when released |
| **Stuck** | The task has likely hung |

### Automation progress and task types

| Phase | Text shown |
| --- | --- |
| Collecting files | *12 file(s) collected* |
| Validating | *Validating 4 / 12 files* |
| Appending | *Appending 12 files* |
| Finalizing | *Finalizing...* |

| Label | What it is |
| --- | --- |
| **Dataset Refresh** | A scheduled cloud dataset refresh |
| **Data Consolidation** | A file consolidation run |
| **File Collection** | A cloud storage file retrieval run |
| **Messaging** | A scheduled email send |
| **Add File as Batch** | Adding a file as a new data batch |
| **Delete Batches** | Batch cleanup |
| **Cloud Storage Retrieval** | Fetching files from cloud storage |
| **Run Pipeline** | Pipeline execution |
| **Tag File** | File tagging during retrieval |

### Active retentions

Below the task rows, **Active Retentions** lists data retention policies that are running. Each row shows the dataset name, **Deleting** or **Suspending** with the rule, and a progress bar of affected batches out of the total. A search box filters by dataset name.

### Fix a task marked Stuck

Mammoth marks a task **Stuck** when it is unlikely to finish on its own:

| Condition | Threshold |
| --- | --- |
| Waiting for Worker | More than 10 minutes |
| Registering Lock | More than 5 minutes |
| Executing | More than 5 hours |
| All tasks Waiting for Lock, none younger than 5 minutes | Straight away |

1. For a pipeline or task row, click the View name to open the View.
2. Look for the **This pipeline has errors** banner and the failing task it points to. For an automation, open it from **Data Library** > **Automations** and read its **Last run result** (for a Data Consolidation, also its **History**).
3. Fix the cause. Common causes are expired connector credentials, a deleted source dataset, or a schema change upstream.
4. Return to Monitor to confirm the next run clears.

The Activity Log records who changed what, not run errors, so it won't show why a run is stuck.

## See what has Auto-sync turned off

The **Paused** tab lists pipeline tasks (joins, lookups, crosstabs and sends to another dataset), exports, Mammoth Managed DB publishes and live links with Auto-sync off. Upstream changes don't flow through them, so downstream datasets may be stale. The tab notes: "Items intentionally paused via Auto-Sync controls. These are working as configured. Review them periodically to ensure nothing is left paused accidentally."

![Paused tab listing four items, each with Source and Auto-sync OFF text and a Turn Auto-sync ON button](https://mammoth.io/docs/images/20260805_050003_M-Paused1.webp)

Each row shows the dataset and View name (a link), the operation type with "Auto-sync OFF", **Paused since** with the date, and **Turn Auto-sync ON**. Rows are sorted by dataset name, then View name. With nothing paused, the tab shows "Nothing paused" and "Every task is syncing automatically."

| Type | What it is |
| --- | --- |
| **Join** | A join task |
| **Lookup** | A lookup task |
| **Crosstab** | A crosstab task |
| **Send to Dataset** | A task that sends data to another dataset |
| **Export (connector name)** | An export to an external destination, for example *Export BigQuery* or *Export Snowflake* |
| **Mammoth Managed DB** | A View published as a Mammoth Managed database |
| **Live link** | A published live data link |

### Turn Auto-sync back on

1. Check that the upstream data is still structurally compatible. Otherwise the task may error straight away.
2. Click **Turn Auto-sync ON**. The button is disabled and the status reads "Auto-sync on, syncing now" while the change applies.
3. The row clears once sync is active.

For the toggle itself, see [Control when Views update with Auto-sync](https://mammoth.io/docs/learn/organise/view-auto-sync/).

## Activity Log tab

The **Activity Log** tab is a chronological record of actions in your workspace, such as creating datasets, editing pipelines, changing automations and connections, and inviting or removing users. It needs the **View Activity Log** workspace permission. If you don't see it, contact your Workspace Owner. See [Activity log](https://mammoth.io/docs/learn/automate/activity-log/).

![Activity Log tab with Project and Workspace buttons, an Export button, and rows for events such as Rerun view and Create dataset](https://mammoth.io/docs/images/20260805_050027_M-AL1.webp)

## Monitor or the notifications bell

Monitor shows the live state of a project. The **Notifications** bell tells you, personally, when something you started or own finishes or fails: an export or download, a data pull, a file a watched folder didn't add, a data check that started failing. Use the bell for "tell me when it's done", and Monitor for "what needs fixing in this project". See [Notifications](https://mammoth.io/docs/learn/automate/notifications/).

## Troubleshooting

| Symptom | Cause | Fix |
| --- | --- | --- |
| A pipeline you started isn't in **Running** | Monitor refreshes every 5 seconds, and fast pipelines can finish before the next poll | Check the View itself |
| "Some of the pending items could not be updated. Please verify them." | One or more batch updates failed | Check each item on its own |
| An automation appears **Stuck** in **Running** | Expired Live Connection credentials, a deleted source dataset, or a file format change in the source folder | Open it from **Data Library** > **Automations** and read **Last run result**. For a Data Consolidation, its **History** lists each file and why it didn't go in |
| A Checkpoint doesn't clear after you approve it | The pipeline resumes after approval, which can take a few minutes | If it doesn't clear, open the pipeline from **Errors** or the Data Editor to check the next run |

## Related

- [Manage automations](https://mammoth.io/docs/learn/automate/manage/): statuses, Last run result and History.
- [Activity log](https://mammoth.io/docs/learn/automate/activity-log/): filter and export the audit trail.
- [Notifications](https://mammoth.io/docs/learn/automate/notifications/): personal alerts for your own jobs.
- [Control when Views update with Auto-sync](https://mammoth.io/docs/learn/organise/view-auto-sync/): what Paused items mean.
- [Fix a failing step](https://mammoth.io/docs/learn/clean-and-shape/fix-a-failing-step/): repair a pipeline error.

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