MetaLens360Help Center

Check sync and fetch status

Use the Org Sync & Repo Fetch Status page to see how fresh each org index and repository is, and review a timeline of every sync, index and fetch run.

Updated in Connections & sync

Overview

Org Sync & Repo Fetch Status (/sync-health) answers one question: how fresh is the data MetaLens360 is analyzing? It covers both Salesforce org indexes and repository branch history, and it is the first place to look when a page seems out of date or a schedule didn't seem to run.

The page has three tabs:

TabWhat it shows
Org Sync & Index HealthIndex coverage per org: components, Apex, triggers, flows, dependencies, last indexed and last sync
Repo Fetch StatusBranch history pulled per repository: last fetch, status, branches, commits stored, duration and trigger
Activity TimelineWhat ran when, across orgs and repositories

Before you start

  • Anyone in the workspace can view this page.
  • Starting an index from it needs the Index / re-index orgs permission (index.run), which every built-in role except Viewer has.

Steps

Check org freshness

  1. Open Org Sync & Repo Fetch Status and select Org Sync & Index Health.
  2. Read the tiles: Orgs, Indexing now, Stale and Never indexed. Green zeros mean everything is current.
  3. Scan the table. Each org's status is Current, Stale (synced since its last index) or Never indexed.
  4. If anything is stale, click Index stale (n). Click Refresh to reload.

Check repository fetches

  1. Select Repo Fetch Status.
  2. Each repository shows Healthy, Failed or Skipped, with when it was last fetched and what triggered it.
  3. For a failure, read the error shown under the repository, and expand the row to see its earlier fetches — one failure and a week of failures need different fixes. Then see Fix Git repository access.

Fetches happen when a sync schedule with an attached repository runs, or when a pipeline is synced by hand from Source Code Repo Insights.

Review the activity timeline

  1. Select Activity Timeline.
  2. Pick a range: Last run (the latest run for every org and repository), Today, Yesterday, Last 7 days, Last 14 days, Last 30 days or Custom.
  3. Use the filter chips Org sync, Org index and Repo fetch to narrow what you see.
  4. Read the summary tiles — Succeeded, Failed, Running and Skipped. Longer ranges are compared against the equally long period before them, so you can spot when things got worse.
  5. Hover over a run to see its exact start time, finish time and duration.

Example

On Monday morning Priya opens Activity Timeline, chooses Last 7 days and filters to Org sync. She sees acme-dev failed every night since Thursday while the other orgs succeeded. In the Sync Center, acme-dev shows Reconnect needed — its sandbox was refreshed. She reconnects it, and the next night's run succeeds.

FAQs

What's the difference between this page and the Sync Center?

The Sync Center is where you start syncs and see recent runs. This page shows freshness and history across orgs and repositories, including indexing and repository fetches.

Why is an org stale if it synced last night?

Its automatic index after the sync may have failed or still be running. Index it again from this page.

Why does the timeline say nothing ran?

Either nothing ran in the selected window, or no schedule is enabled. A quiet window and a paused schedule look the same here, so check Settings → Sync Schedules.

Troubleshooting

A repository shows Skipped

Nothing was attempted for that fetch. Expand the row for the reason, then check the repository connection on the Connections page and the repository fetch attached to your sync schedule.

The Never indexed count doesn't go down

Indexing requires a completed sync. If the org has never synced successfully, sync it first.

An org is missing from the table

Only connected orgs appear. Check the Connections page.

Was this article helpful?

Related articles