MetaLens360Help Center

Audit change data capture usage

See which entities publish change events, which channels carry them and what listens. Find orphaned listeners and capture that nothing in metadata consumes.

Updated in Org inventory & architecture

Overview

Change Data Capture shows which entities publish change events, which channel carries them, and what listens. Salesforce keeps this metadata in four separate places, and MetaLens360 joins it into one view.

Every captured entity uses your daily delivered-event allocation, whether or not anything listens. This page helps you find capture you may not need, and listeners that can never run.

Open it from the sidebar under Overview → Change Data Capture.

Before you start

  • The org must have been synced. The page is built from the org's last metadata sync, not from a live call, so it is exactly as current as that sync. See Run your first sync.
  • Any signed-in workspace member can view the page.

Steps

  1. Pick the org from the selector at the top right. This page keeps its own org choice.
  2. Check the banner under the header. It names the org and shows when its metadata was synced. Confirm it's the org you meant before you draw conclusions.
  3. Read the tiles. Click any of them to jump to the matching section:
    • Entities capturing: objects selected for Change Data Capture, across all channels.
    • With a consumer: entities with at least one Apex trigger, Flow or platform subscriber in metadata.
    • No consumer found: entities that nothing in metadata listens to.
    • Orphaned listeners: Apex triggers on a change event this org doesn't publish. They deploy cleanly and never run.
    • Channels: distinct event channels carrying these entities.
  4. Review Listeners with nothing to listen to first. This is code that can't run.
  5. Review Capturing, with no consumer found. These entities use allocation with no known listener.
  6. Review Capturing, with known consumers and Channels in use to understand the rest.
  7. Read What this analysis cannot see before you switch anything off.

Example

Priya is reviewing event usage in acme-prod because the org is near its delivered-event allocation. The page shows 14 entities capturing and 5 with no consumer found. One orphaned listener is a trigger on Invoice__ChangeEvent, but Invoice__c isn't selected for capture. She checks the integration inventory and confirms that two of the five feed a middleware subscriber. She raises ticket ACME-142 to disable the other three and remove the dead trigger.

FAQs

Does "No consumer found" mean the entity is unused?

No. External subscribers aren't visible in metadata. That includes Pub/Sub API and CometD clients, such as middleware platforms. Treat this as a prompt to investigate, not as proof.

How do I refresh the results?

Re-sync the org. The page always reflects the last metadata sync.

Where do I see the triggers in context?

Map automation and async execution shows CDC triggers alongside the org's other async automation.

Troubleshooting

"No metadata has been synced for this org yet, so there is nothing to analyse. Run a sync first."

Run a sync for the org from Sync Center, then reopen the page.

"No entities are selected for Change Data Capture in acme-uat."

No entities in this org are selected for capture, so CDC isn't using any allocation. If listeners still exist, the page lists them below as orphaned.

"Could not build the CDC inventory for this org."

The stored metadata couldn't be read. Try a full re-sync of the org. See Selective sync and force full resync.

Was this article helpful?

Related articles