> 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/org-insights/automation.md).

# Automation

Analyze dashboards in the Automation tab to understand automation density, API version distribution, unused fields, and object-level complexity.

The Automation tab provides visibility into the declarative and programmatic automation running in your org. It answers a question that Salesforce Setup makes surprisingly difficult: **how much automation do I have, where does it live, and how complex is it?**

For orgs that have evolved over years—accumulating flows, triggers, process builders, and workflow rules—this view is essential for understanding what you're actually working with.

***

## Automation Breakdown by Object

The centerpiece of the Automation tab is an object-level breakdown of all active automation. For each object in your org, Pharos shows the count and type of automation components attached to it.

| Component Type       | What's Counted                                                    |
| -------------------- | ----------------------------------------------------------------- |
| **Flows**            | Record-triggered, screen, scheduled, and auto-launched flows      |
| **Apex Triggers**    | Before and after triggers on the object                           |
| **Process Builders** | Legacy process builder processes (still active in many orgs)      |
| **Workflow Rules**   | Field updates, email alerts, outbound messages, and task creation |

This breakdown immediately reveals which objects carry the heaviest automation load. It's common to find that a handful of objects—often Case, Opportunity, or Account—are disproportionately automated compared to the rest of the org.

{% hint style="info" %}
**Why This Matters:** An object with 19 flows, a process builder, and several workflow rules is a very different maintenance challenge than one with a single trigger. Knowing where complexity concentrates helps you prioritize optimization efforts and assess risk when making changes.
{% endhint %}

***

## Automation vs. Data Volume

The Automation tab doesn't just show automation counts in isolation—it places them alongside **record counts** for each object. This pairing reveals important performance considerations.

```
Object          | Automations | Records
----------------|-------------|----------
Case            | 22          | 15,000
Account         | 8           | 450,000
Custom_Log__c   | 0           | 2,100,000
Opportunity     | 14          | 85,000
```

An object with heavy automation and high record volume is a candidate for performance optimization. Conversely, an object with complex automation but minimal data may be over-engineered—or it may simply be low-traffic, making the automation less of a concern. Record counts on their own also show which objects carry the most data weight, and so where storage optimization efforts should focus.

Record counts may be approximate: when they come from Salesforce record-count statistics, the **Record Count by Object** card says so in a caption. A count shown as **50,000+** means the object has at least 50,000 records. See [Very Large Orgs](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/org-insights/snapshots-and-scans.md#very-large-orgs) for how counts are gathered.

{% hint style="warning" %}
**Performance Hotspots:** If a heavily automated object also appears frequently in your Pharos error logs, that's a strong signal to investigate. The combination of automation density, data volume, and error frequency points toward objects that may need trigger consolidation or flow optimization.
{% endhint %}

***

## API Version Distribution

The Automation tab also analyzes the **API versions** used across your Apex classes, triggers, Visualforce pages, and flows. Each Salesforce API version corresponds to a platform release, and older versions may lack access to newer features or carry deprecated behavior.

| Component             | What's Analyzed                               |
| --------------------- | --------------------------------------------- |
| **Apex Classes**      | API version specified in the class metadata   |
| **Apex Triggers**     | API version specified in the trigger metadata |
| **Visualforce Pages** | API version of the page and its controllers   |
| **Flows**             | API version of the flow definition            |

Ideally, your org should not have too many different API versions in active use. A wide spread—say, classes ranging from API v30 to v60—suggests that legacy code has accumulated without being updated. While older API versions generally continue to work, consolidating toward current versions reduces the surface area for unexpected behavior.

***

## Unused Fields

The Automation tab includes an **unused fields report** that identifies custom fields with no data in the records checked.

When you run the analysis for a specific object, Pharos evaluates each custom field and reports what percentage of records have a value in that field. Fields that are empty on every record checked are flagged as unused and are typically candidates for deprecation.

Fill rates are calculated when you pick an object, not taken from the System Overview snapshot, so they are always current. For objects with up to 50,000 records, the fill rate is exact. Above that, it is the fill rate of a sample of the newest records—close to 50,000 of them—and the chart is labelled with the sample size against the total record count (approximate, or "more than 50,000"), for example "Based on the newest *N* of ≈*M* records".

| Utilization  | Interpretation                                                           |
| ------------ | ------------------------------------------------------------------------ |
| **0%** (red) | Field is empty on every record checked—strong candidate for removal      |
| **1–10%**    | Sparsely populated—may be obsolete or only used in specific record types |
| **10%+**     | Actively in use—proceed with caution before any changes                  |

{% hint style="warning" %}
**0% on Large Objects:** On a sampled object, 0% means no value in the **newest** records checked. A field used only on older records can still show 0%, so confirm the field is truly unused before deleting it.
{% endhint %}

{% hint style="info" %}
**Cleanup Opportunity:** Unused fields contribute to page layout clutter, confuse users, and can make validation rules and automation harder to maintain. Removing them is one of the simplest ways to reduce org complexity—though always verify that no active automation references the field before deleting it.
{% endhint %}

***

## Making Sense of Complexity

The Automation tab gives you the data needed to make informed decisions about where to invest cleanup and optimization effort. Here's how the pieces fit together.

| Observation                                 | What It Suggests                                                                                            |
| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Object with 20+ automations                 | Review for consolidation—multiple flows and triggers on the same object can cause order-of-execution issues |
| High automation + high error rate in Pharos | Strong candidate for refactoring or debugging                                                               |
| Wide API version spread                     | Plan a version update sprint to consolidate toward current API versions                                     |
| Many unused fields on a key object          | Schedule a field cleanup to reduce clutter and simplify maintenance                                         |
| Legacy process builders still active        | Consider migrating to record-triggered flows for better maintainability                                     |

{% hint style="success" %}
**Next Steps:** To review sensitive permission assignments and user access patterns, visit the [Security](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/org-insights/security.md) tab. For overall org health metrics including storage and licensing, see [Org Overview](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/org-insights/org-overview.md).
{% endhint %}
