MetaLens360Help Center

Run your first sync

Pull an org's metadata into MetaLens360 from the Sync Center, follow its progress, and confirm it finished and was indexed so analysis pages have data.

Updated in Connections & sync

Overview

A sync retrieves your org's metadata — Apex, flows, objects, profiles and more — and stores a copy in MetaLens360. Every analysis, comparison and report reads that copy, so a newly connected org shows nothing until its first sync finishes. You run syncs from the Sync Center (/sync).

When a sync completes, MetaLens360 automatically indexes the org (builds the analysis index that pages like Code Intelligence and SOQL Risk read). You can also re-index on demand — see Index an org.

Before you start

  • Connect the org first: Connect a Salesforce org.
  • You need the Run sync on demand permission (sync.run). Every built-in role except Viewer has it.
  • A first sync retrieves everything, so it can take a while on large orgs — often 30–60 minutes. You don't need to keep the page open.

Steps

  1. Open Sync Center from the sidebar. The cards at the top show Connected Orgs, Synced Orgs, Total Components and Active Syncs.
  2. Find your org in the table. A new org shows Never synced in the Last Sync column.
  3. Click Sync Now on that row. The status changes to Queued, then Syncing.
  4. Watch Recent Sync Runs at the bottom of the page. A running sync shows a progress bar and a progress message.
  5. When the run shows Completed, the org's Last Sync updates and its component count appears.
  6. Check the index badge next to Index. It should read "Indexed … ago". If it says Never indexed or "· stale", click Index.
  7. To sync every org at once, click Sync All Orgs at the top. Orgs that are already syncing are skipped.

Example

Priya has just connected acme-prod and acme-uat. She clicks Sync All Orgs. acme-prod starts Syncing and acme-uat waits as Queued for a moment. Forty minutes later both show Completed in Recent Sync Runs, and the index badges read "Indexed 2m ago". She opens Drift Overview to start comparing.

FAQs

What does Re-sync do after the first sync?

Once an org has synced, the button reads Re-sync. It is an incremental sync: it only retrieves metadata types where changes were detected, so it is much faster. Runs of this kind carry an Incremental tag in the history.

Can I sync just a few types?

Yes — use Selective. See Selective and full resync.

Does deleting a sync run delete the metadata?

No. Deleting entries from Recent Sync Runs removes history only; the synced metadata is unaffected.

How do I keep orgs up to date without clicking?

Set up a schedule. See Schedule automatic syncs.

Troubleshooting

The org stays "Queued"

The tooltip explains: "Queued — the sync starts as soon as a sync worker is up. This can take a few minutes." Give it a few minutes. If it fails with "The sync worker never started", run it again.

"<org> is already syncing or queued. Wait for it to complete."

A sync for that org is already running or waiting. You can't start a second one until it finishes.

The run shows Failed

Hover over the Failed chip to read the error, then see Troubleshoot sync failures.

The org shows "Reconnect needed"

Salesforce refused the stored credentials. See Fix expired org credentials.

Was this article helpful?

Related articles