MetaLens360Help Center

Explore a business process with Business Process Explorer

Start from an object and an entry point, then see the full execution graph of a business process with SOQL counts, duplicate queries, caching opportunities and AI explanations per component.

Updated in Code & performance analysis

Overview

Business Process Explorer answers "what runs when this happens?" from the business side. You start from a Salesforce object, choose an entry point — a trigger, Flow or other component that starts the process — and MetaLens360 draws the execution graph from there.

Each node shows how many queries it runs and whether it repeats work done elsewhere, so you can see where a process is expensive without reading every class.

Where Apex Flow Analyzer is built for developers exploring dependencies, Business Process Explorer is a guided, object-first view that suits architects, analysts and release managers.

Before you start

  • The org must be synced and indexed. Index it from Apex Flow Analyzer (Index Org) or Sync Center (Index).
  • AI Explain This Component needs an AI provider in Settings → AI Providers.

Steps

  1. Open Business Processes under Process & Flow.
  2. Pick the org. Until you do, the page says "Select an org above to browse entry points".
  3. Find the object in the left list. Type in Filter objects… to narrow it.
  4. Select the object to see its entry points, then click Trace → on the component you want to start from.
  5. Read the Execution Graph · N components panel. The legend marks Root (the entry point), Async (work that runs in a separate transaction) and Dup (a component that repeats a query).
  6. Click a node to open its details:
    • SOQL Breakdown — each query the component runs, by object.
    • ⚡ Within-Class Cache Opportunities — the same query repeated inside one class, which a simple cache could remove.
    • ⚠ Cross-Class Duplicate Query — the same query issued by a different class in the same process.
  7. Click AI Explain This Component for a plain-language summary of what it does and how to reduce its queries.
  8. Use Back to return to the object list and trace another process.

Example

Priya, a release manager, wants to understand Case escalation on acme-uat before a release. She filters objects to "Case", picks the after-update trigger and clicks Trace →. The graph shows 11 components. Two nodes are marked Dup: both CaseRoutingService and CaseSlaHandler query the same Entitlement records. She opens AI Explain This Component on CaseSlaHandler and adds the suggestion to ACME-142.

FAQs

What counts as an entry point?

A component that starts a process for that object — typically a trigger or a record-triggered Flow.

Why are async nodes highlighted?

Queued, scheduled or event-driven work runs in its own transaction with fresh governor limits. Its queries do not add to the triggering transaction's count.

Does tracing call Salesforce?

No. It reads the index built from your last sync, so re-sync and re-index after deployments.

Troubleshooting

"Failed to load execution tree. Ensure the org is indexed."

Index the org in Apex Flow Analyzer or Sync Center, wait for it to finish, then click Trace → again.

"AI service unavailable. Check that a provider key is configured in Settings → AI Providers."

No AI provider is set up for your workspace, or its key is invalid. Ask an Admin to configure one.

An object I expect is missing from the list

Only objects with indexed entry points appear. Make sure the org was synced recently and re-index.

Was this article helpful?

Related articles