> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementary-data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Incident Merging

When multiple incidents share the same root cause, merging them into a single incident reduces noise and gives your team a unified view of the issue. Elementary supports three ways to merge incidents: manually, through the AI agent, or automatically via merge rules.

## Manual merge

To merge incidents manually:

1. In the incidents list, select two or more open or acknowledged incidents using the checkboxes.
2. Click **Merge** in the floating action menu that appears at the bottom of the screen.
3. On the merge page, choose which incident should be the **primary** — this is the one that survives with all monitors combined.
4. Edit the merged incident's title and summary if needed.
5. Click **Merge Incidents** to confirm.

![Merge page — select primary incident and edit title and description](https://mintcdn.com/elementary/7DFNixRFTAhkEl-2/pics/cloud/incidents_merge_page.png?fit=max\&auto=format\&n=7DFNixRFTAhkEl-2\&q=85\&s=164f01ebd842e69f4c1d47b67ad47a4a)

Merge page — select primary incident and edit title and description

After merging:

* The primary incident stays open and inherits all monitors from the merged incidents.
* The merged incidents are resolved with reason "Merged" and hidden from the main list.
* A "Merged" chip appears on the primary incident in the list view when it contains multiple monitors.

## Auto-merge rules

Auto-merge rules let Elementary automatically group related failures into incidents without manual intervention. Each rule can be enabled or disabled independently for an environment.

To configure auto-merge rules, click the **gear icon** on the incidents page to open the settings menu.

### Asset run errors

When enabled, asset runs that fail with the same error can be grouped into one incident, even when there are no freshness issues. For example, model runs that fail because of the same missing table can share an incident.

Related freshness issues can join that incident when they open within one day of an active asset run failure and the affected assets are connected through lineage. If a freshness issue is equally close to multiple eligible incidents, it stays separate.

### Tests connected by lineage

When enabled, failed tests of the same type on connected upstream or downstream assets and columns can be grouped into one incident.

### Similar test errors

When enabled, failed tests can be grouped when they share the same error, such as a missing table, or have similar, informative error messages. Generic messages alone do not cause tests to be grouped. This rule applies to test errors; asset run errors use the **Asset run errors** rule.

### Freshness issues

When enabled, freshness incidents affecting the same upstream source are automatically merged into a single incident. This is useful when a source goes stale and causes freshness failures across many downstream tables — instead of creating a separate incident for each table, they are grouped together.

The rule requires at least two freshness failures from the same source within a one-day window before merging them.

## AI agent-assisted merge

[AI Triage & Resolution](https://docs.elementary-data.com/cloud/ai-agents/ai-triage-resolution.md) can investigate multiple open incidents, identify shared root causes, and propose merging them. When the agent suggests a merge:

1. A merge plan appears in the chat with the selected incidents and a proposed primary.
2. Review the plan and click **Confirm** to proceed.
3. You are taken to the merge page with everything pre-filled, where you can make final edits before merging.

This is particularly useful when you have many open incidents and want to quickly identify which ones are related.

## Splitting incidents (undo a merge)

If monitors were incorrectly merged, you can split them back out:

1. Open the merged incident and go to the **Monitors** tab.
2. Select the monitors you want to detach using the checkboxes.
3. Click **Detach** and confirm.

Each detached monitor becomes a new open incident. If all monitors are detached, the original incident is resolved.

## How merged incidents appear

| Where | What you see |
| - | - |
| **Incidents list** | A "Merged" chip on incidents with multiple monitors. Merged child incidents are hidden — only the primary shows. |
| **Merged child incident** | An info banner at the top: "This incident has been merged into \[primary incident]" with a link to the primary. The incident is read-only. |
| **Monitors tab** | All monitors from merged incidents appear on the primary incident. |
| **Timeline** | Events showing when monitors were added from or removed to other incidents, with links. |
| **Quick filters** | Use the "Merged" quick filter to show only incidents that contain multiple monitors. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.