MetaLens360Help Center

Map automation and async execution

See every trigger, queueable, batch, schedulable, future method, event and callout in an org. Trace async chains, watch live jobs, and find trigger conflicts and dead code.

Updated in Org inventory & architecture

Overview

Automation & Execution Architecture shows how work runs in an org. You can see what starts it, how it hops across async boundaries, and what is running right now. It also flags managed-package risk, objects with more than one trigger, and code that nothing calls.

Open it from the sidebar under Overview → Automation Architecture. If you have an old bookmark to /org-architect, it now opens this page.

Before you start

  • The org must be synced and indexed. The blueprint, conflicts and dead-code views read the local index. See Index an org.
  • Live Activity calls the org directly, so it needs a working connection.
  • The component chat needs an AI provider.
  • Any signed-in workspace member can view the page.

Steps

  1. Pick the org in the header. Its data loads automatically. Click Refresh to reload it later.
  2. Read the tiles: Triggers, Queueables, Batch Classes, Schedulables, @future Methods, Platform Events, CDC Events and Ext. Callouts. Click any tile to drill into that component type.
  3. On Async Blueprint, choose a view:
    • Chain Explorer traces execution from each entry point. Expand a row to follow each hop.
    • Chain Risk Map lists every async chain with depth 3 or more, sorted by risk. Each hop resets the governor context, and chains with callouts are rated higher.
    • Component Registry lists every component, filtered by type.
  4. Open Live Activity to see Active Jobs (queued or running async jobs) and Scheduled Jobs (all scheduled Apex).
  5. Open Managed Packages for a risk assessment of installed packages.
  6. Open Trigger Conflicts to find objects with more than one trigger.
  7. Open Dead Code to see components grouped as Safe to Delete, Dynamic Call Risk and Excluded (have callers).
  8. Click any component name to see its source and an AI chat. The chat opens with "Explain what this component does". Type in Ask a follow-up… to keep going.

Example

Priya notices acme-prod hitting async limits at month end. In Chain Risk Map, she finds a chain where a trigger runs a queueable that starts a batch, which then makes a callout. That is four hops, with a callout at the end. She opens the trigger, asks "What would break if this ran synchronously?", and records the answer in ticket ACME-142.

FAQs

Why doesn't Live Activity match the other tabs?

Live Activity is read directly from the org when you load it. The other tabs come from the last sync and index.

Is more than one trigger on an object always a problem?

Not always, but Salesforce doesn't guarantee the order in which multiple triggers on the same object run. Trigger Conflicts lists them so you can decide whether to consolidate.

Where are change data capture listeners covered in detail?

See Audit change data capture usage. It joins entities, channels and listeners.

Troubleshooting

"No access token stored for this org. Go to Connections, test the connection, then come back."

Live Activity needs a working token. Open Connections, test the org's connection, and reconnect it if the test fails. See Fix expired org credentials.

All the tiles show 0

The org hasn't been indexed, or its index is empty. Run a sync, then index the org. See Pages show no data.

"No deep chains detected."

This is good news. No async chain reaches depth 3.

Was this article helpful?

Related articles