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

# Ontology Compatibility

> Keep artifact types, mappings, enrichment rules, and matching strategies in sync with ontology revisions

## Overview

Ontology changes are versioned. Each time you save a schema change, Experio publishes a new **revision**
and checks every configuration that depends on that schema:

* Content types (Artifact Types)
* Data mappings
* Enrichment rules
* Matching strategies

Configs that no longer match the ontology are flagged. **Invalid** configs **block ingestion** until you
fix them. **Stale** configs warn only — scans still run.

Navigate to **Admin > Graph > Compatibility**, or open **History** from the [Ontology](/admin-guide/ontology)
editor.

## Statuses

| Status             | Meaning                                                                          | Ingestion              |
| ------------------ | -------------------------------------------------------------------------------- | ---------------------- |
| **Valid**          | Checked against the current ontology revision                                    | Allowed                |
| **Stale**          | Names were auto-updated after an ontology rename; review the config              | Allowed (warning only) |
| **Pending review** | Needs an admin to confirm the config still looks right                           | Allowed (warning only) |
| **Invalid**        | References an entity, attribute, or relationship that is missing or incompatible | **Blocked**            |

Invalid examples include a deleted ontology attribute that a content type still extracts, or an
enrichment rule whose output field is no longer on the target entity.

## Compatibility dashboard

The dashboard summarizes counts for valid, stale, invalid, and pending-review configs. Filter the
table to **Needs attention**, **Invalid**, **Stale**, or **Review**, then open a row to edit that
configuration.

Use **Revision history** on the dashboard (or **History** on the ontology editor) to inspect past
schema publishes. See [Ontology](/admin-guide/ontology#revision-history-and-rollback).

## Fixing an invalid or stale config

On the edit screen for a content type, mapping, enrichment rule, or matching strategy:

1. Read the **compatibility issues** listed on the page (each issue names the missing or renamed
   ontology element).
2. Update the configuration so it matches the current ontology — or restore the ontology element if
   the deletion was a mistake (see rollback on the ontology page).
3. Click **Re-validate** to re-check against the current revision.
4. For **stale** or **pending review** after a rename that already looks correct, click
   **Mark as reviewed** to return the status to **valid** without editing the schema.

## Blocked scans

Starting a job (scan, file upload, classification, or enrichment run) fails immediately when a linked
config is **invalid**. The error lists the blocking configs with links to their admin pages. No
RabbitMQ message is published.

The **Data Sources** list shows a computed compatibility column from linked content types and
mappings, so you can see a problem before you click Start Job.

<Warning>
  Stale configs do **not** block ingestion. Invalid configs do. Fix invalid items before you rely on
  scheduled or OAuth-triggered scans.
</Warning>

## Setup health

The admin home (**Admin**) shows a setup-health strip:

* **Green** — all tracked configs are valid
* **Amber** — some configs are stale or pending review (ingestion still runs)
* **Red** — at least one config is invalid (ingestion is blocked for linked sources)

The strip links to this compatibility dashboard.

## Related pages

* [Ontology](/admin-guide/ontology) — save impact, history, and rollback
* [Content Types](/admin-guide/content-types)
* [Data Mapping](/admin-guide/data-mapping)
* [Enrichment Rules](/admin-guide/enrichment-rules)
* [Matching Strategies](/admin-guide/matching-strategies)
* [Data Sources](/admin-guide/data-sources)