> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/change-tracking/tracked-metadata.md).

# Tracked Metadata

View the list of metadata types that Pharos tracks as part of change tracking.

Pharos Change Tracking monitors the metadata components that matter most for understanding your org's behavior. The focus is on **automation, code, and structural configuration**—the areas where changes are most likely to impact functionality and cause errors.

{% hint style="info" %}
**Not Everything, But the Important Stuff:** Pharos tracks the most impactful metadata categories rather than attempting to capture every metadata type in the org. This keeps the repository focused and the change history meaningful.
{% endhint %}

***

## Tracked Categories

### Automation

Automation components are the most common source of errors when changes are made. A modified flow, an updated process builder, or a refactored trigger can have cascading effects across the org.

| Metadata Type       | Description                                                               |
| ------------------- | ------------------------------------------------------------------------- |
| **Flows**           | Screen flows, record-triggered flows, autolaunched flows, scheduled flows |
| **Process Builder** | Process builder definitions and their associated actions                  |
| **Workflow Rules**  | Workflow rule criteria and associated actions                             |

### Code

Code changes are tracked at the source level, providing full diffs that show exactly which lines were added, modified, or removed.

| Metadata Type                | Description                                                                |
| ---------------------------- | -------------------------------------------------------------------------- |
| **Apex Classes**             | All Apex class source code, including controllers, services, and utilities |
| **Apex Triggers**            | Trigger source code for all objects                                        |
| **Lightning Web Components** | LWC JavaScript, HTML, and CSS files                                        |
| **Aura Components**          | Aura component bundles                                                     |
| **Visualforce Pages**        | Visualforce markup and associated controllers                              |

### Object Metadata

Object-level changes affect how data is structured and validated. These changes can silently break integrations, automations, and user workflows.

| Metadata Type        | Description                                              |
| -------------------- | -------------------------------------------------------- |
| **Custom Objects**   | Object definitions, including settings and configuration |
| **Custom Fields**    | Field definitions, types, formulas, and default values   |
| **Validation Rules** | Validation rule criteria and error messages              |
| **Page Layouts**     | Layout assignments and field arrangements                |

***

## Why These Categories?

The tracked categories are chosen based on where changes most frequently cause issues in production environments.

```mermaid
graph TD
    subgraph High["High Impact"]
        H1[Automation: Flows, PB, Triggers]
        H2[Apex Code]
    end
    subgraph MedHi["Med-High Impact"]
        M1[Validation Rules]
    end
    subgraph Medium["Medium Impact"]
        M2[Object & Field Changes]
        M3[LWC / Aura Components]
    end
    subgraph Low["Low Impact"]
        L1[Page Layouts]
        L2[Profiles & Permissions]
        L3[Reports & Dashboards]
    end
    High --> MedHi --> Medium --> Low
```

Pharos focuses on the top of this spectrum—the metadata types that are most likely to introduce errors when modified.

{% hint style="warning" %}
**Not Currently Tracked:** Certain metadata types such as profiles, permission sets, reports, dashboards, and static resources are not included in Change Tracking. These may be added in future releases.
{% endhint %}

***

## What Gets Captured

For each tracked component, Pharos stores the **complete metadata definition**—not just a change notification. This means you can:

| Capability                     | Description                                                                   |
| ------------------------------ | ----------------------------------------------------------------------------- |
| **View full diffs**            | See exactly which lines changed, with additions and removals highlighted      |
| **Browse historical versions** | Navigate to any point in time and see the full component as it existed then   |
| **Compare across time**        | Use GitHub's compare feature to diff any two points in your org's history     |
| **Search across components**   | Use GitHub search to find references, dependencies, or specific code patterns |

***

## Real-World Use Cases

### Debugging a New Error

A new Issue appears in Pharos affecting the Account object. You check the GitHub repository and find that a validation rule on Account was modified two hours ago—adding a required field that existing integrations aren't populating.

### Understanding Automation Complexity

By browsing the repository, you can see the full picture of automation on any object—all the flows, triggers, and process builders in one place. This is especially valuable when onboarding new team members.

### Auditing Changes Over Time

Need to know what changed in your org last month? Browse the commit history filtered by date range to see every metadata modification, who made it, and exactly what was different.

{% hint style="success" %}
**Tip:** Combine Change Tracking data with Pharos's error timeline to quickly identify cause-and-effect relationships between metadata changes and new errors.
{% endhint %}

***

## Relationship to AI Analysis

The metadata stored through Change Tracking serves a dual purpose. Beyond providing a historical audit trail, it acts as the **knowledge base for Pharos's AI analysis engine**.

When the AI analyzes an error, it can:

* **Read the actual source code** of the Apex class or flow that generated the error
* **Examine recent changes** to determine if a modification could be the cause
* **Analyze dependencies** between components to understand the blast radius of a change

This all happens by reading from the GitHub repository—avoiding additional API calls to your org and enabling faster, more detailed analysis.

→ [Learn more about AI Analysis](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ai-analysis.md)

→ [Back to Change Tracking overview](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/change-tracking.md)

{% hint style="success" %}
**Next Step:** Explore [AI Analysis](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ai-analysis.md) to learn how Pharos leverages your tracked metadata for intelligent error investigation.
{% endhint %}
